Communication control system, server device, and communication control method

ABSTRACT

A pairing server includes: a second determination unit which, when a first request is received from a transmitting terminal and a second request is received from a receiving terminal, determines whether or not there is matching of pairing identifiers included in the first and second requests and whether or not there is matching of communication device information included in the first and second requests; and a pairing unit which pairs the transmitting terminal and the receiving terminal using a first device identifier included in the first request and a second device identifier included in the second request when it is determined that there is matching of the pairing identifiers included in the first and second requests and that there is matching of the communication device information included in the first and second requests.

TECHNICAL FIELD

The present invention relates to a communication control system, aserver device, and a communication control method which are adapted forpairing communication devices to control communication therebetween.

BACKGROUND ART

In recent years, digital still cameras and digital video cameras havebeen in widespread use, and users increasingly accumulate captureddigital photo data and digital video data (hereinafter referred to as“photos” and “video”) in a communication device (hereinafter referred toas “terminal”) such as a personal computer (PC) to view them. Along withthe widespread use of the Internet, more and more terminals areconnected to the network, and content data (hereinafter referred to as“content”) such as the photos and video accumulated in the terminals isexchanged via the network.

In photos and video, objects which entail privacy concerns, such ashuman faces and residences, often appear. When sharing photos and videowith a friend, it is therefore necessary to check and set a destinationin advance so as not to transmit the content to an unintended recipient.

For example, Patent Literature (PTL) 1 discloses a photo sharing systemfor sharing photos between television receivers. In the photo sharingsystem in PTL 1, photos can be shared between persons who knowpredetermined identification information (ID).

CITATION LIST Patent Literature [PTL 1]

-   International Publication No. 2008/093781

SUMMARY OF INVENTION Technical Problem

However, the above conventional technique does not make it possible toreduce the occurrence of mistaken sharing of content.

Thus, the main object of the present invention is to provide acommunication control system, a sever device, and a communicationcontrol method which can reduce the occurrence of mistaken sharing ofcontent.

In order to achieve the object, a communication control system accordingto an aspect of the present invention comprises a first communicationdevice; a second communication device; a third communication devicecapable of communicating with the first communication device; a fourthcommunication device capable of communicating with the secondcommunication device and the third communication device; and a serverdevice connected to each of the first communication device and thesecond communication device via a network, wherein the communicationcontrol system pairs the first communication device and the secondcommunication device to control communication between the firstcommunication device and the second communication device, the thirdcommunication device includes: a management unit configured to holdcommunication device information that is information on the fourthcommunication device; and a first transmitting unit configured totransmit the held communication device information to the firstcommunication device, the first communication device includes: a pairingidentifier generation unit configured to generate a pairing identifierwhen the communication device information is received from the thirdcommunication device; a second transmitting unit configured to transmit,to the server device, a first request including a first deviceidentifier of the first communication device, the communication deviceinformation, and the generated pairing identifier; and a thirdtransmitting unit configured to transmit the generated pairingidentifier to the third communication device, the third communicationdevice further includes a fourth transmitting unit configured to, whenthe pairing identifier is received from the first communication device,transmit the received pairing identifier to the fourth communicationdevice, the fourth communication device includes a fifth transmittingunit configured to, when the pairing identifier is received from thethird communication device, transmit communication device informationand the received pairing identifier to the second communication device,the communication device information being information on the fourthcommunication device which is previously held in the fourthcommunication device, the second communication device includes a sixthtransmitting unit configured to transmit a second request to the serverdevice when the communication device information and the pairingidentifier are received from the fourth communication device, the secondrequest including a second device identifier of the second communicationdevice, the received communication device information, and the receivedpairing identifier, and the server device includes: a determination unitconfigured to, when the first request is received from the firstcommunication device and the second request is received from the secondcommunication device, determine whether or not the pairing identifierincluded in the first request and the pairing identifier included in thesecond request match and whether or not the communication deviceinformation included in the first request and the communication deviceinformation included in the second request match; and a pairing unitconfigured to pair the first communication device and the secondcommunication device using the first device identifier included in thefirst request and the second device identifier included in the secondrequest when it is determined that the pairing identifier included inthe first request and the pairing identifier included in the secondrequest match and that the communication device information included inthe first request and the communication device information included inthe second request match.

It is to be noted that these general or specific aspects may beimplemented using a device, a method, an integrated circuit, a computerprogram, or a recording medium, or any combination of devices, methods,integrated circuits, computer programs, and recording mediums.

Advantageous Effects of Invention

According to an aspect of the present invention, it is possible toreduce the occurrence of mistaken sharing of content.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram showing a configuration of a conventionalcommunication control system.

FIG. 2 is a flowchart for explaining the operation in the conventionalcommunication control system.

FIG. 3A is a block diagram showing a configuration of a communicationcontrol system in Embodiment 1.

FIG. 3B is a block diagram showing a detailed configuration of a pairingserver in Embodiment 1.

FIG. 4 shows an example of data managed by a phase management unit of atransmitting terminal in Embodiment 1.

FIG. 5 shows an example of data managed by a phase management unit of areceiving terminal in Embodiment 1.

FIG. 6A shows an example of a pairing management table stored in apairing management unit of the pairing server in Embodiment 1.

FIG. 6B shows an example of a communication device management tablestored in a communication device management unit of the pairing serverin Embodiment 1.

FIG. 7 is a flowchart for explaining an outline of processing of thecommunication control system in Embodiment 1.

FIG. 8A is a flowchart showing a flow of processing at a pairingpreparation phase in Embodiment 1.

FIG. 8B is a flowchart showing a flow of processing at the pairingpreparation phase in Embodiment 1.

FIG. 9 shows an example of message data included in a pairing startmessage in Embodiment 1.

FIG. 10 shows an example of an address data display in Embodiment 1.

FIG. 11 shows an example of message data included in a pairing startresponse message in Embodiment 1.

FIG. 12 shows an example of message data included in a pairing requestmessage in Embodiment 1.

FIG. 13 shows an example of data stored in the pairing management unitof the pairing server in Embodiment 1.

FIG. 14 shows a screen of a transmitting mobile phone which appearsafter a message input in Embodiment 1.

FIG. 15A is a flowchart showing a flow of processing at a pairingfinalization phase in Embodiment 1.

FIG. 15B is a flowchart showing a flow of processing at a pairingfinalization phase in Embodiment 1.

FIG. 16 shows an example of message data included in a pairingfinalization start message in Embodiment 1.

FIG. 17 shows an example of message data included in a pairingfinalization request message in Embodiment 1.

FIG. 18 shows an example of the pairing management table in Embodiment1.

FIG. 19 shows an example of message data included in a pairingfinalization response message in Embodiment 1.

FIG. 20 shows an example of the data stored in the phase management unitof the receiving terminal in Embodiment 1.

FIG. 21 is a flowchart showing a flow of processing at a communicationdevice registration phase in Embodiment 1.

FIG. 22 shows an example of message data included in a communicationdevice registration start message in Embodiment 1.

FIG. 23 shows an example of message data included in a communicationdevice registration request message in Embodiment 1.

FIG. 24 shows an example of the communication device management table inEmbodiment 1.

FIG. 25 shows an example of message data included in a communicationdevice registration response message in Embodiment 1.

FIG. 26 is a block diagram showing an example of a registrationcompletion display in Embodiment 1.

FIG. 27A is a block diagram showing a configuration of a communicationcontrol system in Embodiment 2.

FIG. 27B is a block diagram showing a detailed configuration of apairing server in Embodiment 2.

FIG. 28 is a flowchart for explaining an outline of processing of thecommunication control system in Embodiment 2.

FIG. 29A is a flowchart showing a flow of processing at a pairingpreparation phase in Embodiment 2.

FIG. 29B is a flowchart showing a flow of processing at the pairingpreparation phase in Embodiment 2.

FIG. 30 shows an example of message data included in a pairing requestmessage in Embodiment 2.

FIG. 31 shows an example of the pairing management table in Embodiment2.

FIG. 32 shows an example of message data included in a pairing requestresponse message in Embodiment 2.

FIG. 33A is a block diagram showing a configuration of a communicationcontrol system in Embodiment 3.

FIG. 33B is a block diagram showing a detailed configuration of apairing server in Embodiment 3.

FIG. 34 is a flowchart for explaining an outline of processing of thecommunication control system in Embodiment 3.

FIG. 35A is a flowchart showing a flow of processing at a pairingpreparation phase in Embodiment 3.

FIG. 35B is a flowchart showing a flow of processing at the pairingpreparation phase in Embodiment 3.

FIG. 36 shows an example of message data included in a pairing startmessage in Embodiment 3.

FIG. 37A is a block diagram showing a configuration of a communicationcontrol system in Embodiment 4.

FIG. 37B is a block diagram showing a detailed configuration of apairing server in Embodiment 4.

FIG. 38 is a flowchart for explaining an outline of processing of thecommunication control system in Embodiment 4.

FIG. 39A is a flowchart showing a flow of processing at a pairingpreparation phase in Embodiment 4.

FIG. 39B is a flowchart showing a flow of processing at the pairingpreparation phase in Embodiment 4.

FIG. 40 shows an example of message data included in a pairing startresponse message in Embodiment 4.

FIG. 41 shows an example of message data included in a pairing requestmessage in Embodiment 4.

FIG. 42 shows an example of the pairing management table in Embodiment4.

FIG. 43A is a flowchart showing a flow of processing at a pairingfinalization phase in Embodiment 4.

FIG. 43B is a flowchart showing a flow of processing at a pairingfinalization phase in Embodiment 4.

FIG. 44 shows an example of message data included in a pairingfinalization start message in Embodiment 4.

FIG. 45 shows an example of message data included in a pairingfinalization request message in Embodiment 4.

FIG. 46 shows an example of the pairing management table in Embodiment4.

FIG. 47A is a block diagram showing a configuration of a communicationcontrol system in Embodiment 5.

FIG. 47B is a block diagram showing a detailed configuration of apairing server in Embodiment 5.

FIG. 48 is a flowchart for explaining an outline of processing of thecommunication control system in Embodiment 5.

FIG. 49A is a flowchart showing a flow of processing at a pairingpreparation phase in Embodiment 5.

FIG. 49B is a flowchart showing a flow of processing at the pairingpreparation phase in Embodiment 5.

FIG. 50 shows an example of message data included in a pairing startmessage in Embodiment 5.

FIG. 51 shows an example of message data included in a pairing startresponse message in Embodiment 5.

FIG. 52A is a flowchart showing a flow of processing at a pairingfinalization phase in Embodiment 5.

FIG. 52B is a flowchart showing a flow of processing at a pairingfinalization phase in Embodiment 5.

FIG. 53 shows an example of message data included in a pairingfinalization start message in Embodiment 5.

DESCRIPTION OF EMBODIMENTS Underlying Knowledge Forming Basis of thePresent Invention

First, the photo sharing system in PTL 1 is described.

FIG. 1 is a block diagram showing a configuration of a conventionalphoto sharing system 100.

In FIG. 1, the photo sharing system 100 includes a transmitting terminal101, a receiving terminal 102, and a photo sharing server 103. Thetransmitting terminal 101 is a communication device which is operated bya sender of a photo, and the receiving terminal 102 is a communicationdevice which is operated by a recipient of the photo. The photo sharingserver 103 is a server device which issues ID to the transmittingterminal 101 and in which photos to be shared are accumulated.

FIG. 2 is a flowchart for explaining the operation in the conventionalphoto sharing system 100. Specifically, FIG. 2 shows how to check andset a destination before photo-sharing.

In Step S201, the transmitting terminal 101 transmits, to the photosharing server 103, a request for issuing shared ID. The photo sharingserver 103 then generates shared ID and transmits the generated sharedID to the transmitting terminal 101 in Step S202.

In Step S203, the transmitting terminal 101 receives the shared ID fromthe photo sharing server 103 and displays the received shared ID on ascreen. The sender notifies the recipient of the shared ID displayed onthe screen. The notification is made using a telephone and so on. InStep S204, the receiving terminal 102 receives an input of the shared IDfrom the recipient who has been notified of the shared ID.

The above description is made on the conventional way to check and set adestination.

Furthermore, in the photo sharing system in PTL 1, in the case oftransmitting a photo of a sender from the transmitting terminal 101 tothe receiving terminal 102, the transmitting terminal 101 transmits, tothe photo sharing server 103, the shared ID and the photo desired to betransmitted. The photo sharing server 103 accumulates the receivedshared ID and photo in such a way that the received shared ID and photoare associated with each other. Afterward, the receiving terminal 102transmits, to the photo sharing server 103, the shared ID set inadvance, and receives, from the photo sharing server 103, the photoassociated with the shared ID, thereby receiving the photo of thesender.

However, in the photo sharing system in PTL 1, photos sometimes cannotbe correctly shared. For example, the sender and the recipient areunable to share photos when the sender notifies the recipient ofincorrect shared ID or when the recipient inputs incorrect shared IDinto the receiving terminal 102.

In such a case, the recipient fails to share the photo of the sender.Furthermore, the receiving terminal 102 can receive the photo associatedwith the incorrectly input shared ID, which is problematic. Furthermore,when a malicious recipient inputs arbitrary shared ID into the receivingterminal 102, the receiving terminal 102 can receive the photoassociated with that shared ID, which is also problematic.

In other words, the technique of PTL 1 has a problem that datatransmitted from the transmitting terminal can be received by thereceiving terminal which is not intended to receive the data. This meansthat the data is transmitted to a recipient who is not intended by asender, which poses a significant privacy problem.

Furthermore, the recent widespread use of mobile phones allows manypeople to use the short message service (SMS), the multimedia messagingservice (MMS), mobile phone emails, and so on as communication means forindividuals. Thus, the sender presumably generally uses thesecommunication means to notify the recipient of the shared ID in the formof electronic information such as text information. Furthermore, themobile phones are equipped with wired transmission means, such as theuniversal serial buses (USB), and wireless transmission means, such asthe near field communication (NFC) and Wi-Fi, and it is thereforepossible to easily transmit the shared ID from the communication deviceto the mobile phones and from the mobile phones to the communicationdevice.

However, since the communication means, such as SMS, easily transfersthe electronic information received by the recipient to another person,a malicious recipient who receives the shared ID from the sender cantransfer the shared ID to another person, and when the other personinputs the transferred shared ID into the receiving terminal 102, thereceiving terminal 102 can receive the photo associated with the sharedID, which is also problematic.

Thus, a general or specific aspect of the present invention has anobject to reduce, in pairing the first communication device and thesecond communication device, the occurrence of pairing of the firstcommunication device or the second communication device with othercommunication device which is not intended.

A communication control system according to an aspect of the presentinvention comprises a first communication device; a second communicationdevice; a third communication device capable of communicating with thefirst communication device; a fourth communication device capable ofcommunicating with the second communication device and the thirdcommunication device; and a server device connected to each of the firstcommunication device and the second communication device via a network,wherein the communication control system pairs the first communicationdevice and the second communication device to control communicationbetween the first communication device and the second communicationdevice, the third communication device includes: a management unitconfigured to hold communication device information that is informationon the fourth communication device; and a first transmitting unitconfigured to transmit the held communication device information to thefirst communication device, the first communication device includes: apairing identifier generation unit configured to generate a pairingidentifier when the communication device information is received fromthe third communication device; a second transmitting unit configured totransmit, to the server device, a first request including a first deviceidentifier of the first communication device, the communication deviceinformation, and the generated pairing identifier; and a thirdtransmitting unit configured to transmit the generated pairingidentifier to the third communication device, the third communicationdevice further includes a fourth transmitting unit configured to, whenthe pairing identifier is received from the first communication device,transmit the received pairing identifier to the fourth communicationdevice, the fourth communication device includes a fifth transmittingunit configured to, when the pairing identifier is received from thethird communication device, transmit communication device informationand the received pairing identifier to the second communication device,the communication device information being information on the fourthcommunication device which is previously held in the fourthcommunication device, the second communication device includes a sixthtransmitting unit configured to transmit a second request to the serverdevice when the communication device information and the pairingidentifier are received from the fourth communication device, the secondrequest including a second device identifier of the second communicationdevice, the received communication device information, and the receivedpairing identifier, and the server device includes: a determination unitconfigured to, when the first request is received from the firstcommunication device and the second request is received from the secondcommunication device, determine whether or not the pairing identifierincluded in the first request and the pairing identifier included in thesecond request match and whether or not the communication deviceinformation included in the first request and the communication deviceinformation included in the second request match; and a pairing unitconfigured to pair the first communication device and the secondcommunication device using the first device identifier included in thefirst request and the second device identifier included in the secondrequest when it is determined that the pairing identifier included inthe first request and the pairing identifier included in the secondrequest match and that the communication device information included inthe first request and the communication device information included inthe second request match.

With this structure, the first communication device and the secondcommunication device are paired when a set of the pairing identifier andthe communication device information which have been transmitted fromthe first communication device to the server device matches a set of thepairing identifier and the communication device information which havebeen transmitted from the second communication device to the serverdevice. Thus, the occurrence of mistaken pairing of other communicationdevices which perform another pairing process with the firstcommunication device or the second communication device is reduced. Inother words, it is possible to reduce the occurrence of mistaken sharingof content.

Furthermore, with this structure, whether or not there is matching ofnot only the pairing identifiers, but also the communication deviceinformation is determined. Consequently, even when a malicious recipientreceives the pairing identifier from the sender, transfers the pairingidentifier to another person, and the other person inputs thetransferred pairing identifier into other communication devices, theoccurrence of pairing of the other communication devices with the firstcommunication device or the second communication device can be reduced.In other words, the occurrence of mistaken sharing of content withothers can be reduced.

For example, it may be that the communication device informationindicates a communication address of the fourth communication device,and the fourth transmitting unit is configured to transmit the pairingidentifier to the fourth communication device using the communicationaddress indicated in the communication device information.

With this structure, the communication address of the fourthcommunication device can be used as the communication device informationon the fourth communication device. Thus, it is possible to reduce theoccurrence of overlapping of the communication device information on thefourth communication device with the communication device information onother communication devices. As a result, mistaken sharing of contentwith others can be further prevented.

For example, it may be that the first communication device furtherincludes a first data conversion unit configured to convert thecommunication device information using a one-way function, the firstrequest includes the communication device information resulting from theconversion, the second communication device further includes a seconddata conversion unit configured to convert the communication deviceinformation using the one-way function, and the second request includesthe communication device information resulting from the conversion.

With this structure, the communication device information convertedusing a one-way function is transmitted, which makes it possible toprevent the communication device information before conversion fromleaking.

For example, it may be that the first transmitting unit is configured totransmit the communication device information to the first communicationdevice using near field communication, and the third transmitting unitis configured to transmit the pairing identifier to the thirdcommunication device using the near field communication.

With this structure, the first communication device and the thirdcommunication device communicate with each other using the near fieldcommunication, which allows for an improvement in user convenience.

Furthermore, a communication control system according to an aspect ofthe present invention comprises: a first communication device; a secondcommunication device; a third communication device capable ofcommunicating with the first communication device; a fourthcommunication device capable of communicating with the secondcommunication device and the third communication device; and a serverdevice connected to each of the first communication device and thesecond communication device via a network, wherein the communicationcontrol system pairs the first communication device and the secondcommunication device to control communication between the firstcommunication device and the second communication device, the thirdcommunication device includes: a management unit configured to holdcommunication device information that is information on the fourthcommunication device; and a first transmitting unit configured totransmit the held communication device information to the firstcommunication device, the first communication device includes a secondtransmitting unit configured to transmit, to the server device, a firstrequest including a first device identifier of the first communicationdevice, and the communication device information received from the thirdcommunication device, the server device includes: a pairing identifiergeneration unit configured to generate a pairing identifier; and a thirdtransmitting unit configured to transmit the generated pairingidentifier to the first communication device, the first communicationdevice further includes a fourth transmitting unit configured totransmit, to the third communication device, the pairing identifierreceived from the server device, the third communication device furtherincludes a fifth transmitting unit configured to, when the pairingidentifier is received from the first communication device, transmit thereceived pairing identifier to the fourth communication device, thefourth communication device includes a sixth transmitting unitconfigured to, when the pairing identifier is received from the thirdcommunication device, transmit communication device information and thereceived pairing identifier to the second communication device, thecommunication device information being information on the fourthcommunication device which is previously held in the fourthcommunication device, the second communication device includes a seventhtransmitting unit configured to transmit a second request to the serverdevice when the communication device information and the pairingidentifier are received from the fourth communication device, the secondrequest including a second device identifier of the second communicationdevice, the received communication device information, and the receivedpairing identifier, the server device further includes: a determinationunit configured to, when the first request is received from the firstcommunication device and the second request is received from the secondcommunication device, determine whether or not the pairing identifiergenerated by the pairing identifier generation unit and the pairingidentifier included in the second request match and whether or not thecommunication device information included in the first request and thecommunication device information included in the second request match;and a pairing unit configured to pair the first communication device andthe second communication device using the first device identifierincluded in the first request and the second device identifier includedin the second request when it is determined that the pairing identifiergenerated by the pairing identifier generation unit and the pairingidentifier included in the second request match and that thecommunication device information included in the first request and thecommunication device information included in the second request match.

With this structure, the server device is capable of generating thepairing identifier. Even in such a case, it is possible to produce thesame effects as those in the above communication control system.

Furthermore, a communication control system according to an aspect ofthe present invention comprises: a first communication device; a secondcommunication device; a third communication device capable ofcommunicating with the first communication device; a fourthcommunication device capable of communicating with the secondcommunication device and the third communication device; and a serverdevice connected to each of the first communication device and thesecond communication device via a network, wherein the communicationcontrol system pairs the first communication device and the secondcommunication device to control communication between the firstcommunication device and the second communication device, the thirdcommunication device includes: a pairing identifier generation unitconfigured to generate a pairing identifier; a management unitconfigured to hold communication device information that is informationon the fourth communication device; and a first transmitting unitconfigured to transmit, to the first communication device, the pairingidentifier generated by the pairing identifier generation unit and theheld communication device information, the first communication deviceincludes: a second transmitting unit configured to transmit, to theserver device, a first request including a first device identifier ofthe first communication device, and the communication device informationand the pairing identifier received from the fourth communicationdevice; and a third transmitting unit configured to transmit the pairingidentifier to the third communication device, the third communicationdevice further includes a fourth transmitting unit configured totransmit, to the fourth communication device, the pairing identifiergenerated by the pairing identifier generation unit, the fourthcommunication device includes a fifth transmitting unit configured to,when the pairing identifier is received from the third communicationdevice, transmit communication device information and the receivedpairing identifier to the second communication device, the communicationdevice information being information on the fourth communication devicewhich is previously held in the fourth communication device, the secondcommunication device includes a sixth transmitting unit configured totransmit a second request to the server device when the communicationdevice information and the pairing identifier are received from thefourth communication device, the second request including a seconddevice identifier of the second communication device, the receivedcommunication device information, and the received pairing identifier,the server device includes: a determination unit configured to, when thefirst request is received from the first communication device and thesecond request is received from the second communication device,determine whether or not the pairing identifier included in the firstrequest and the pairing identifier included in the second request matchand whether or not the communication device information included in thefirst request and the communication device information included in thesecond request match; and a pairing unit configured to pair the firstcommunication device and the second communication device using the firstdevice identifier included in the first request and the second deviceidentifier included in the second request when it is determined that thepairing identifier included in the first request and the pairingidentifier included in the second request match and that thecommunication device information included in the first request and thecommunication device information included in the second request match.

With this structure, the third communication device is capable ofgenerating the pairing identifier. Even in such a case, it is possibleto produce the same effects as those in the above communication controlsystem.

Furthermore, a communication control system according to an aspect ofthe present invention comprises: a first communication device; a secondcommunication device; a third communication device capable ofcommunicating with the first communication device; a fourthcommunication device capable of communicating with the secondcommunication device and the third communication device; and a serverdevice connected to each of the first communication device and thesecond communication device via a network, wherein the communicationcontrol system pairs the first communication device and the secondcommunication device to control communication between the firstcommunication device and the second communication device, the thirdcommunication device includes: a management unit configured to holdcommunication device information that is information on the fourthcommunication device; and a first transmitting unit configured totransmit the held communication device information to the firstcommunication device, the first communication device includes: a pairingidentifier generation unit configured to generate a pairing identifierwhen the communication device information is received from the thirdcommunication device; a first conversion unit configured to convert,using a predetermined conversion method, the communication deviceinformation received from the third communication device, to generatefirst converted data; a second transmitting unit configured to transmit,to the server device, a first request including a first deviceidentifier of the first communication device and the generated pairingidentifier; and a third transmitting unit configured to transmit thepairing identifier and the first converted data to the thirdcommunication device, the third communication device further includes afourth transmitting unit configured to, when the pairing identifier andthe first converted data are received from the first communicationdevice, transmit the received pairing identifier and the received firstconverted data to the fourth communication device, the fourthcommunication device includes a fifth transmitting unit configured to,when the pairing identifier and the first converted data are receivedfrom the third communication device, transmit communication deviceinformation, the received pairing identifier, and the received firstconverted data to the second communication device, the communicationdevice information being information on the fourth communication devicewhich is previously held in the fourth communication device, the secondcommunication device includes: a second conversion unit configured to,when the communication device information, the pairing identifier, andthe first converted data are received from the fourth communicationdevice, convert the communication device information using thepredetermined conversion method, to generate second converted data; afirst determination unit configured to determine whether or not thefirst converted data and the second converted data match; and a sixthtransmitting unit configured to transmit a second request to the serverdevice when it is determined that the first converted data and thesecond converted data match, the second request including a seconddevice identifier of the second communication device and the pairingidentifier, and the server device includes: a second determination unitconfigured to, when the first request is received from the firstcommunication device and the second request is received from the secondcommunication device, determine whether or not the pairing identifierincluded in the first request and the pairing identifier included in thesecond request match; and a pairing unit configured to pair the firstcommunication device and the second communication device using the firstdevice identifier included in the first request and the second deviceidentifier included in the second request when it is determined that thepairing identifier included in the first request and the pairingidentifier included in the second request match.

With this structure, the second communication device is capable ofdetermining whether or not the conversed data based on the communicationdevice information match. Even in such a case, it is possible to producethe same effects as those in the above communication control system.

Furthermore, a communication control system according to an aspect ofthe present invention comprises: a first communication device; a secondcommunication device; a third communication device capable ofcommunicating with the first communication device; a fourthcommunication device capable of communicating with the secondcommunication device and the third communication device; and a serverdevice connected to each of the first communication device and thesecond communication device via a network, wherein the communicationcontrol system pairs the first communication device and the secondcommunication device to control communication between the firstcommunication device and the second communication device, the firstcommunication device includes: a pairing identifier generation unitconfigured to generate a pairing identifier; a first transmitting unitconfigured to transmit, to the server device, a first request includinga first device identifier of the first communication device and thegenerated pairing identifier; and a second transmitting unit configuredto transmit the pairing identifier to the third communication device,the third communication device includes: a management unit configured tohold communication device information that is information on the fourthcommunication device; a first conversion unit configured to convert theheld communication device information using a predetermined conversionmethod, to generate first converted data; and a third transmitting unitconfigured to, when the pairing identifier is received from the firstcommunication device, transmit the received pairing identifier and thefirst converted data to the fourth communication device, the fourthcommunication device includes: a second conversion unit configured toconvert communication device information using the predeterminedconversion method, to generate second converted data, when the pairingidentifier and the first converted data are received from the thirdcommunication device, the communication device information beinginformation on the fourth communication device which is previously heldin the fourth communication device; a first determination unitconfigured to determine whether or not the first converted data and thesecond converted data match; and a fourth transmitting unit configuredto transmit the received pairing identifier to the second communicationdevice when it is determined that the first converted data and thesecond converted data match, the second communication device includes afifth transmitting unit configured to transmit a second request to theserver device when the pairing identifier is received from the fourthcommunication device, the second request including a second deviceidentifier of the second communication device and the received pairingidentifier, and the server device includes: a second determination unitconfigured to, when the first request is received from the firstcommunication device and the second request is received from the secondcommunication device, determine whether or not the pairing identifierincluded in the first request and the pairing identifier included in thesecond request match; and a pairing unit configured to pair the firstcommunication device and the second communication device using the firstdevice identifier included in the first request and the second deviceidentifier included in the second request when it is determined that thepairing identifier included in the first request and the pairingidentifier included in the second request match.

With this structure, the fourth communication device is capable ofdetermining whether or not the conversed data based on the communicationdevice information match. Even in such a case, it is possible to producethe same effects as those in the above communication control system.

Furthermore, a server device according to an aspect of the presentinvention is a server device connected to each of a first communicationdevice and a second communication device via a network, for pairing thefirst communication device and the second communication device tocontrol communication between the first communication device and thesecond communication device, the server device comprising: adetermination unit configured to, when a first request which requestspairing is received from the first communication device and a secondrequest which requests pairing is received from the second communicationdevice, determine whether or not a pairing identifier included in thefirst request and a pairing identifier included in the second requestmatch and whether or not communication device information included inthe first request and communication device information included in thesecond request match, the communication device information beinginformation on a device capable of communicating with the secondcommunication device; and a pairing unit configured to pair the firstcommunication device and the second communication device using the firstdevice identifier included in the first request and the second deviceidentifier included in the second request when it is determined that thepairing identifier included in the first request and the pairingidentifier included in the second request match and that thecommunication device information included in the first request and thecommunication device information included in the second request match.

This structure can provide the same effects as the above communicationcontrol system.

It is to be noted that these general or specific aspects may beimplemented using a system, a device, a method, an integrated circuit, acomputer program, or a recording medium, or any combination of systems,devices, methods, integrated circuits, computer programs, and recordingmedia.

Embodiments of the present invention are described below with referenceto the drawings.

It is to be noted that each of Embodiments described below illustratesone specific example of the present invention. Numeric values, shapes,materials, constituents, positions and topologies of the constituents,steps, an order of the steps, and the like in the following Embodimentsare an example, and it should therefore not be construed that thepresent invention is limited to each of these Embodiments. Furthermore,out of the constituents in the following Embodiments, the constituentsnot stated in the independent claims describing the broadest concept ofthe present invention are described as arbitrary constituents.

Embodiment 1

FIG. 3A is a block diagram showing a configuration of a communicationcontrol system 300 in Embodiment 1. FIG. 3B is a block diagram showing adetailed configuration of a pairing server 314 in Embodiment 1.

As shown in FIG. 3A, the communication control system 300 includes atransmitting terminal 301, a receiving terminal 308, the pairing server314 connected to each of the transmitting terminal 301 and the receivingterminal 308 via the network, for example, a transmitting mobile phone319, and a receiving mobile phone 323.

The transmitting terminal 301 corresponds to the first communicationdevice and holds content such as photos. The transmitting terminal 301includes a data conversion unit 302, a device connection unit 304, aterminal ID holding unit 307, a communication unit 305, and a phasemanagement unit 306.

The receiving unit 308 corresponds to the second communication deviceand receives content such as photos from the transmitting terminal 301and displays it. The receiving terminal 308 includes a communication309, a phase management unit 310, a data conversion unit 311, a deviceconnection unit 312, and a terminal ID holding unit 313.

The pairing server 314 corresponds to the server device and pairs thetransmitting terminal 301 and the receiving terminal 308 permitted toreceive the content transmitted from the transmitting terminal 301. Thepairing server 314 includes a pairing management unit 315, a phasemanagement unit 316, and a communication unit 317.

The transmitting mobile phone 319 corresponds to the third communicationdevice and provides wired or wireless connection with the transmittingterminal 301 to exchange data therebetween. Furthermore, thetransmitting mobile phone 319 communicates with the receiving mobilephone 323 by using a communication means such as SMS. The transmittingmobile phone 319 includes a device connection unit 320, a communicationunit 321, and an address management unit 322.

The receiving mobile phone 323 corresponds to the fourth communicationdevice and provides wired or wireless connection with the receivingterminal 308 to exchange data therebetween. Furthermore, the receivingmobile phone 323 communicates with the transmitting mobile phone 319 byusing a communication means such as SMS. The receiving mobile phone 323includes an address management unit 324, a communication unit 325, and adevice connection unit 326.

Each of the constituent units of the transmitting terminal 301 isdescribed.

The data conversion unit 302 is an operational circuit which convertsdata, such as addresses of mobile phone emails, using a one-way functionto generate converted data. As the one-way function, the hash functionSHA-256 is used, for example. It is to be noted that a conversion methodusing the one-way function is an example of a predetermined conversionmethod. This means that the data conversion unit 302 does not alwaysneed to use the one-way function to convert the addresses.

A pairing value generation unit 303 is an operational circuit whichgenerates a pairing value that is used for pairing. In this embodiment,the pairing value generation unit 303 corresponds to the pairingidentifier generation unit.

Pairing means associating the transmitting terminal 301 that transmitscontent such as photos, with the receiving terminal 308 that receivesthe content, in order to control communication between the twoterminals, i.e., the transmitting terminal 301 and the receivingterminal 308. In this embodiment, pairing also means limiting thetransmission and receiving of the content only to the two terminalswhich are associated with each other. In other words, two terminalsshare content as a result of pairing in this embodiment.

Furthermore, the pairing value is an example of a pairing identifier andis a number sequence in this embodiment. The pairing identifier does notalways need to be a number sequence and may include a character or asymbol, for example.

The device connection unit 304 is a communication circuit whichcommunicates with the transmitting mobile phone 319 to exchange emailaddresses or pairing values for use in pairing and which is implementedas a communication interface such as USB or NFC. For example, the deviceconnection unit 304 communicates with the transmitting mobile phone 319using the near field communication. In this embodiment, the deviceconnection unit 304 corresponds to the third transmitting unit whichtransmits various data to the transmitting mobile phone 319.

The communication unit 305 is a communication circuit implemented as anetwork interface which provides communication of the pairing value, theterminal ID, and so on, with the pairing server 314. In this embodiment,the communication unit 305 corresponds to the second transmitting unitwhich transmits various data to the pairing server 314.

The phase management unit 306 manages communication phases. Thecommunication phases include a pairing preparation phase at which thetransmitting terminal 301 transmits pairing information to the pairingserver 314 and a pairing finalization phase at which such an associationis finalized.

FIG. 4 shows an example of data managed by the phase management unit 306of the transmitting terminal 301. In FIG. 4, management ID 401 is anidentifier for identifying a set of a communication phase, a pairingvalue, and receiving terminal ID.

A communication phase 402 indicates which one of the pairing preparationphase and the pairing finalization phase is the current communicationphase. Here, “1” is stored in the communication phase 402 when thecurrent communication phase is the pairing preparation phase, and “2” isstored in the communication phase 402 when the current communicationphase is the pairing finalization phase. It is to be noted that theabove values are an example and any value may be used as long as theycan identify the two phases.

In a pairing value 403, a pairing value generated by the transmittingterminal 301 using the pairing value generation unit 303 is stored

In receiving terminal ID 404, terminal ID of the receiving terminal 308paired with the transmitting terminal 301 is stored when the pairing isfinalized.

The terminal ID holding unit 307 is a memory circuit implemented as aflash memory which holds identification information unique to theterminal. The terminal ID is written in the terminal ID holding unit 307at the factory before shipment or is written in the terminal ID holdingunit 307 through the communication unit 305 via the network aftershipment from the factory, depending on the case.

Subsequently, each of the constituent units of the receiving terminal308 is described.

The communication unit 309 is a communication circuit implemented as anetwork interface which provides communication of the pairing value, theterminal ID, and so on, with the pairing server 314. In this embodiment,the communication unit 309 corresponds to the sixth transmitting unitwhich transmits various data to the server device.

The phase management unit 310 manages communication phases. Thecommunication phases include a pairing preparation phase at which thereceiving terminal 308 transmits pairing information to the pairingserver 314 and a pairing finalization phase at which such an associationis finalized.

FIG. 5 shows an example of data managed by the phase management unit 310of the receiving terminal 308. In FIG. 5, management ID 501 is anidentifier for identifying a set of a communication phase, a pairingvalue, and transmitting terminal ID.

A communication phase 502 indicates which one of the pairing preparationphase and the pairing finalization phase is the current communicationphase. Here, “1” is stored in the communication phase 502 when thecurrent communication phase is the pairing preparation phase, and “2” isstored in the communication phase 502 when the current communicationphase is the pairing finalization phase. It is to be noted that theabove values are an example and any value may be used as long as theycan identify the two phases.

In a pairing value 503, the pairing value received from the receivingmobile phone 323 is stored.

In transmitting terminal ID 504, terminal ID of the transmittingterminal 301 paired with the receiving terminal 308 is stored when thepairing is finalized.

The data conversion unit 311 is an operational circuit which convertsdata, such as addresses of mobile phone emails, using a one-wayfunction. As the one-way function, the hash function SHA-256 is used,for example. The data conversion unit 311 converts data using the sameconversion method as the data conversion unit 302 of the transmittingterminal 301.

The device connection unit 312 is a communication circuit whichcommunicates with the receiving mobile phone 323 to exchange emailaddresses or pairing values for use in pairing and which is implementedas a communication interface such as USB or NFC.

The terminal ID holding unit 313 is a memory circuit implemented as aflash memory which holds identification information unique to theterminal. The terminal ID is written in the terminal ID holding unit 313at the factory before shipment or is written in the terminal ID holdingunit 313 through the communication unit 309 via the network aftershipment from the factory, depending on the case.

Next, each of the constituent units of the pairing server 314 isdescribed.

The pairing management unit 315 corresponds to the storage unit forstoring the pairing value and is, for example, a memory device such ashard disk drive (HDD). The pairing management unit 315 stores a pairingmanagement table 315 a that is used to pair the transmitting terminal301 and the receiving terminal 308 permitted to receive the contenttransmitted from the transmitting terminal 301.

FIG. 6A shows an example of the pairing management table 315 a stored inthe pairing management unit 315. As shown in FIG. 6A, the pairingmanagement table 315 a includes receiving terminal ID 601, transmittingterminal ID 602, a communication phase 603, a pairing value 604, and aconverted address value 605.

In the receiving terminal ID 601, the terminal ID of the receivingterminal 308 received from the receiving terminal 308 via thecommunication unit 317 is stored. In the transmitting terminal ID 602,the terminal ID of the transmitting terminal 301 received from thetransmitting terminal 301 via the communication unit 317 is stored. Thecommunication phase 603 indicates which one of the pairing preparationphase and the pairing finalization phase is the current communicationphase. Here, “1” is stored in the communication phase 603 when thecurrent communication phase is the pairing preparation phase, and “2” isstored in the communication phase 603 when the current communicationphase is the pairing finalization phase. In the pairing value 604, thepairing value received from the transmitting terminal 301 via thecommunication unit 317 is stored. In the converted address value 605, aconverted receiving-side address value received from the transmittingterminal 301 via the communication unit 317 is stored. In FIG. 6A, ablank column indicates that no value is stored yet.

It is to be noted that the pairing management unit 315 does not alwaysneed to store the pairing value and the converted address value into atable like the pairing management table 315 a. In other words, thepairing management unit 315 may store the pairing value and theconverted address value in any form as long as the pairing value and theconverted address value can be stored in association with each other.

The phase management unit 316 is an electronic circuit for managingcommunication phases. As shown in FIG. 3B, the phase management unit 316includes a first storing unit 316 a, a second storing unit 316 b, afirst determination unit 316 c, a second determination unit 316 d, and apairing unit 316 e. A detail of each of the constituent units will bedescribed later.

The communication unit 317 is a communication circuit implemented as anetwork interface which provides communication of the pairing value andthe terminal ID with the transmitting terminal 301 and the receivingterminal 308.

A communication device management unit 318 is a memory device such asHDD, for example. The communication device management unit 318 storesinformation on the transmitting mobile phone 319 registered in thetransmitting terminal 301. As shown in FIG. 6B, a communication devicemanagement table 318 a includes terminal ID 606 and a convertedcommunication device value 607.

In the terminal ID 606, the terminal ID received from the transmittingterminal 301 and the receiving terminal 308 via the communication unit317 is stored. In the converted communication device value 607, theconverted communication device value received from the transmittingterminal 301 and the receiving terminal 308 via the communication unit317. In FIG. 6B, a blank column indicates that no value is stored yet.

Furthermore, each of the constituent units of the transmitting mobilephone 319 is described.

The device connection unit 320 is a communication circuit whichcommunicates with the transmitting terminal 301 to exchange emailaddresses or pairing values for use in pairing and which is implementedas a communication interface such as USB or NFC. For example, the deviceconnection unit 320 communicates with the transmitting terminal 301using the near field communication. In this embodiment, the deviceconnection unit 320 corresponds to the first transmitting unit whichtransmits communication device information to the first communicationdevice.

A communication unit 321 is a communication circuit which is implementedas a communication interface that transmits information by way of SMS,MMS, or the like. For example, the communication unit 321 transmits datato the receiving mobile phone 323 using a communication address of thereceiving mobile phone 323 which is held in the address management unit322. In this embodiment, the communication unit 321 corresponds to thefourth transmitting unit which transmits the pairing identifier to thefourth communication device.

The address management unit 322 holds and manages a communicationaddress of a user of the transmitting mobile phone 319 and acommunication address of an information recipient which are used totransmit information from the user by way of SMS, MMS, or the like. Inthis embodiment, this communication address corresponds to thecommunication device information. This means that the address managementunit 322 corresponds to the management unit which holds thecommunication device information that is information on the fourthcommunication device. The address management unit 322 is a storagedevice or a memory circuit, such as HDD or a flash memory. In thefollowing, the communication address is referred to also simply as anaddress or as address data.

Lastly, each of the constituent units of the receiving mobile phone 323is described.

The address management unit 324 holds and manages an address of a userof the receiving mobile phone 323 and an address of an informationrecipient which are used to transmit information from the user by way ofSMS, MMS, or the like. This means that the address management unit 324previously holds the communication device information that isinformation on the receiving mobile phone 323. The address managementunit 324 is a storage device or a memory circuit such as HDD or a flashmemory.

The communication unit 325 is a communication circuit which isimplemented as a communication interface that transmits information byway of SMS, MMS, or the like.

The device connection unit 326 is a communication circuit whichcommunicates with the receiving terminal 308 to exchange email addressesor pairing values for use in pairing and which is implemented as acommunication interface such as USB or NFC. In this embodiment, thedevice connection unit 326 corresponds to the fifth transmitting unit.

Next, various operations in the communication control system 300configured as above are specifically described.

FIG. 7 is a flowchart for explaining an outline of processing of thecommunication control system 300 in Embodiment 1. The processing of thecommunication control system 300 includes three phases: a communicationdevice registration phase; a pairing preparation phase; and a pairingfinalization phase.

The communication device registration phase is processing which isperformed first. At this communication device registration phase, a setof a mobile phone and a terminal which are used for pairing isregistered in the pairing server.

The pairing preparation phase is processing which is performed followingthe communication device registration phase. At this pairing preparationphase, a sender transmits information necessary for pairing to arecipient by using a communication means such as SMS or MMS.

The pairing finalization phase is processing which is performedfollowing the pairing preparation phase. At this pairing finalizationphase, pairing is finalized using the information necessary for pairingwhich the recipient received from the sender.

The following describes the pairing preparation phase, the pairingfinalization phase, and the communication device registration phase inthis order with reference to the drawings.

FIGS. 8A and 8B are a flowchart showing a flow of processing at thepairing preparation phase. With reference to FIGS. 8A and 8B, variousprocessing at the pairing phase is described.

(Step S801)

According to an instruction of a sender, the transmitting mobile phone319 transmits a pairing start message to the transmitting terminal 301.Here, a specific example of the pairing start message is described.

FIG. 9 shows an example of message data included in the pairing startmessage. A pairing start message 901 includes, as the message data, amessage identifier 902, a version 903, transmitting mobile phone ID 904,a sender address 905, and an address of target recipient 906.

The message identifier 902 is message data for identifying the messagewhich is exchanged between the transmitting mobile phone 319 and thetransmitting terminal 301.

The version 903 is message data for identifying a version number of thepairing start message. When the message data included in the messagehave any change such as addition or deletion due to system expansion,the version number is increased. Each of the mobile phone and theterminal compares a value of the version number included in the messagewith the version number which the device itself supports, to therebydetermine whether to be able to handle the message.

The transmitting mobile phone ID 904 is message data indicating theterminal ID of the transmitting mobile phone 319 which transmits thepairing start message. The terminal ID of the mobile phone is a uniqueidentifier assigned by a mobile-phone operator.

The sender address 905 is address data which the sender uses in SMS,MMS, or the like, and is stored in the address management unit 322 ofthe transmitting mobile phone 319.

The address of target recipient 906 is address data of SMS, MMS, or thelike which indicate a recipient with whom the sender wishes to sharephotos, etc., and is stored in the address management unit 322 of thetransmitting mobile phone 319.

The sender selects a menu “sharing setting (send)” on the menu screen ofthe transmitting mobile phone 319. Upon selection of the menu “sharingsetting (send)”, the transmitting mobile phone 319 displays, on thescreen, the address data stored in the address management unit 322. FIG.10 shows a display example of the address data. The sender selects thetarget recipient with whom the sender wishes to share photos, etc., fromamong the addresses displayed on the screen.

Upon selection of the target recipient, the transmitting mobile phone319 generates the pairing start message 901. The transmitting mobilephone 319 sets, for example, “1001” indicating the pairing startmessage, “0100” indicating a default version, unique ID “FFEEDDCCBBAA .. . ” assigned by an operator, an MMS address of the sender“suzukixxx.ne.jp”, and an MMS address of the target recipient“yamamotoxxx.ne.jp”, for the message identifier 902, the version 903,the transmitting mobile phone ID 904, the sender address 905, and theaddress of target recipient 906, respectively. Afterward, thetransmitting mobile phone 319 transmits the generated pairing startmessage 901 to the transmitting terminal 301.

The transmission of the pairing start message 901 to the transmittingterminal 301 is performed through the device connection unit 320 of thetransmitting mobile phone 319 and the device connection unit 304 of thetransmitting terminal 301.

(Step S802)

The pairing value generation unit 303 of the transmitting terminal 301generates a pairing value. The pairing value is a random number valuewhich is sufficiently large, and is set as “123456789ABCDEF0” in thisembodiment. The pairing value may be generated after the pairing startmessage 901 is received and may alternatively have been generated inadvance.

The phase management unit 306 stores the generated pairing value inassociation with a phase number. For the phase number, “1” indicatingthe pairing preparation phase is stored.

(Step S803)

The phase management unit 306 of the transmitting terminal 301 transmitsa pairing start response message to the transmitting mobile phone 319.Here, a specific example of the pairing start response message isdescribed.

FIG. 11 shows an example of message data included in the pairing startresponse message. A pairing start response message 1101 includes, as themessage data, a message identifier 1102, a version 1103, and a pairingvalue 1104.

The message identifier 1102 is message data for identifying the messagewhich is exchanged between the transmitting mobile phone 319 and thetransmitting terminal 301. The version 1103 is message data foridentifying a version number of the pairing start response message. Thepairing value 1104 is message data indicating the pairing valuegenerated in Step S802.

The phase management unit 316 generates such pairing start responsemessage 1101. In generating the pairing start response message 1101, thephase management unit 316 sets, for example, “1002” indicating thepairing start response message, “0100” indicating a default version, andthe pairing value “123456789ABCDEF0” generated in Step S802, for themessage identifier 1102, the version 1103, and the pairing value 1104,respectively.

The transmission of the pairing start response message 1101 to thetransmitting mobile phone 319 is performed through the device connectionunit 304 of the transmitting terminal 301 and the device connection unit320 of the transmitting mobile phone 319.

(Step S804)

The data conversion unit 302 of the transmitting terminal 301 generatesa converted address value (converted data) based on the address oftarget recipient included in the pairing start message 901 received fromthe transmitting mobile phone 319. In this embodiment, the convertedaddress value is an output value which results from input of the addressof target recipient to an SHA-256 operational circuit in the dataconversion unit 302.

(Step S805)

The data conversion unit 302 of the transmitting terminal 301 generatesa converted communication device value based on the terminal ID of thetransmitting terminal 301 which is held in the terminal ID holding unit307, and the transmitting mobile phone ID received from the transmittingmobile phone 319. In this embodiment, the converted communication devicevalue is an output value which results from input of a combined valuegenerated by combining the terminal ID of the transmitting terminal 301and the transmitting mobile phone ID, to the SHA-256 operational circuitin the data conversion unit 302.

(Step S806)

The phase management unit 306 of the transmitting terminal 301 transmitsa pairing request message to the pairing server 314. This pairingrequest message corresponds to the first request. Here, a specificexample of the pairing request message is described.

FIG. 12 shows an example of message data included in the pairing requestmessage. A pairing request message 1201 includes, as the message data, amessage identifier 1202, a version 1203, transmitting terminal ID 1204,a pairing value 1205, a converted address value 1206, and a convertedcommunication device value 1207.

The message identifier 1202 is message data for identifying the messagewhich is exchanged between the transmitting terminal 301 and the pairingserver 314. The version 1203 is message data for identifying a versionnumber of the pairing request message. The transmitting terminal ID 1204is message data indicating the terminal ID of the transmitting terminal301 that is a terminal which transmits the pairing request message. Thepairing value 1205 is message data indicating the pairing valuegenerated in Step S802. The converted address value 1206 is message dataindicating the converted address value generated in Step S804. Theconverted communication device value 1207 is message data indicating theconverted communication device value generated in Step S805.

The phase management unit 306 generates such pairing request message1201. In generating the pairing request message 1201, the phasemanagement unit 306 sets, for example, “0001” indicating the pairingrequest message, “0100” indicating a default version, the terminal ID tobe held in the terminal ID holding unit 307, the pairing value generatedin Step S802, the converted address value generated in Step S804, andthe converted communication device value generated in Step S805, for themessage identifier 1202, the version 1203, the transmitting terminal ID1204, the pairing value 1205, the converted address value 1206, and theconverted communication device value 1207, respectively. Afterward, thephase management unit 306 transmits the generated pairing requestmessage 1201 to the pairing server 314 via the communication unit 305.

(Step S807)

The first determination unit 316 c of the pairing server 314 determineswhether or not a set of the transmitting terminal ID and the convertedcommunication device value which are included in the received pairingrequest message 1201 has been stored in the communication devicemanagement table 318 a. When the set of the transmitting terminal ID andthe converted communication device value has been stored, the processingin Step S808 is performed next. When the set of the transmittingterminal ID and the converted communication device value has not beenstored, the pairing server 314 transmits an error message to thetransmitting terminal 301, thereby ending the processing.

(Step S808)

When receiving the pairing request message 1201 from the transmittingterminal 301 via the communication unit 317, the second storing unit 316b of the pairing server 314 stores, into the pairing management table315 a, the phase number, the transmitting terminal ID included in thereceived pairing request message 1201, the pairing value, and theconverted address value in association with one another. The secondstoring unit 316 b stores, for the phase number, “1” indicating thepairing preparation phase.

FIG. 13 shows an example of the pairing management table 315 a at theend of Step S808. In FIG. 13, the column for the receiving terminal IDis blank as no value has been set yet.

(Step S809)

After receiving the pairing start response message 1101 from thetransmitting terminal 301 in Step S803, the transmitting mobile phone319 displays a send screen for an MMS message which is directed to thetarget recipient designated in Step S801 by the sender on the menu“sharing setting (send)”, and accepts a message input from the sender.FIG. 14 shows a screen example which appears after the message input.

After completion of the message input from the sender, the transmittingmobile phone 319 transmits an MMS message to the target recipientdesignated in Step S801 by the sender. At this time, the pairing valueincluded in the pairing start response message received from thetransmitting terminal 301 in Step S803 is attached to the MMS message tobe transmitted.

The description on processing at the pairing preparation phase endshere.

Subsequently, processing at the pairing finalization phase is describedwith reference to FIGS. 15A and 15B.

FIGS. 15A and 15B are a flowchart showing a flow of processing at thepairing finalization phase.

(Step S1501)

The recipient receives the MMS message from the sender. Afterward, thereceiving mobile phone 323 transmits a pairing finalization startmessage to the receiving terminal 308 according to an instruction of therecipient. Here, a specific example of the pairing finalization startmessage is described.

FIG. 16 shows an example of message data included in the pairingfinalization start message. A pairing finalization start message 1601includes, as the message data, a message identifier 1602, a version1603, receiving mobile phone ID 1604, a recipient address 1605, and apairing value 1606.

The message identifier 1602 is message data for identifying the messagewhich is exchanged between the receiving mobile phone 323 and thereceiving terminal 308.

The version 1603 is message data for identifying a version number of thepairing finalization start message.

The receiving mobile phone ID 1604 is message data indicating theterminal ID of the receiving mobile phone 323 which transmits thepairing finalization start message. The terminal ID of the mobile phoneis a unique identifier assigned by a mobile-phone operator.

The recipient address 1605 is address data which the recipient uses inSMS, MMS, or the like, and is stored in the address management unit 324of the receiving mobile phone 323.

The pairing value 1606 is message data indicating the pairing valuereceived from the transmitting mobile phone 319.

The receiving mobile phone 323 generates the pairing finalization startmessage 1601 according to an instruction of the recipient. The receivingmobile phone 323 sets, for example, “1003” indicating the pairingfinalization start message, “0100” indicating a default version, uniqueID “EEDDCCBBAA99 . . . ” assigned by an operator, an MMS address of therecipient “yamamotoxxx.ne.jp”, and the pairing value attached to the MMSmessage received from the sender, for the message identifier 1602, theversion 1603, the receiving mobile phone ID 1604, the recipient address1605, and the pairing value 1606, respectively. Afterward, the receivingmobile phone 323 transmits the generated pairing finalization startmessage 1601 to the receiving terminal 308.

The transmission of the pairing finalization start message 1601 to thereceiving terminal 308 is performed through the device connection unit326 of the receiving mobile phone 323 and the device connection unit 312of the receiving terminal 308.

(Step S1502)

The data conversion unit 311 of the receiving terminal 308 generates aconverted address value (converted data) based on the recipient addressincluded in the pairing finalization start message 1601 received fromthe receiving mobile phone 323. In this embodiment, the convertedaddress value is an output value which results from input of therecipient address to an SHA-256 operational circuit in the dataconversion unit 311.

(Step S1503)

The data conversion unit 311 of the receiving terminal 308 generates aconverted communication device value based on the terminal ID of thereceiving terminal 308 which is held in the terminal ID holding unit313, and the receiving mobile phone ID received from the receivingmobile phone 323. In this embodiment, the converted communication devicevalue is an output value which results from input of a combined valuegenerated by combining the terminal ID of the receiving terminal 308 andthe receiving mobile phone ID, to the SHA-256 operational circuit in thedata conversion unit 311.

(Step S1504)

The phase management unit 306 of the receiving terminal 308 stores, inassociation with the phase number, the pairing value included in areceived pairing finalization start message 1401. As the phase number,“1” indicating the pairing preparation phase is stored, for example.Afterward, the phase management unit 306 transmits a pairingfinalization request message to the pairing server 314. This pairingfinalization request message corresponds to the second request. Here, aspecific example of the pairing finalization request message isdescribed.

FIG. 17 shows an example of message data included in the pairingfinalization request message. A pairing finalization request message1701 includes, as the message data, a message identifier 1702, a version1703, receiving terminal ID 1704, a pairing value 1705, a convertedaddress value 1706, and a converted communication device value 1707.

The message identifier 1702 is message data for identifying the messagewhich is exchanged between the receiving terminal 308 and the pairingserver 314. The version 1703 is message data for identifying a versionnumber of the pairing finalization request message. The receivingterminal ID 1704 is message data indicating the terminal ID of thereceiving terminal 308 that is a terminal which transmits the pairingfinalization request message. The pairing value 1705 is message dataindicating the pairing value received from the receiving mobile phone323. The converted address value 1706 is message data indicating theconverted address value generated in Step S1502. The convertedcommunication device value 1707 is message data indicating the convertedcommunication device value generated in Step S1503.

The phase management unit 310 generates such pairing finalizationrequest message 1701. In generating the pairing finalization requestmessage 1701, the phase management unit 310 sets, for example, “0003”indicating the pairing finalization request message, “0100” indicating adefault version, the terminal ID to be held in the terminal ID holdingunit 313, the pairing value received from the receiving mobile phone323, the converted address value generated in Step S1502, and theconverted communication device value generated in Step S1503, for themessage identifier 1702, the version 1703, the receiving terminal ID1704, the pairing value 1705, the converted address value 1706, and theconverted communication device value 1707, respectively. Afterward, thephase management unit 310 transmits the generated pairing finalizationrequest message 1701 to the pairing server 314 via the communicationunit 309.

(Step S1505)

The first determination unit 316 c of the pairing server 314 determineswhether or not a set of the receiving terminal ID and the convertedcommunication device value which are included in the received pairingfinalization request message 1701 has been stored in the communicationdevice management table 318 a. When the set of the receiving terminal IDand the converted communication device value has been stored, theprocessing in Step S1507 is performed next. When the set of thereceiving terminal ID and the converted communication device value hasnot been stored, the pairing server 314 transmits an error message tothe receiving terminal 308, thereby ending the processing.

(Step S1506)

When receiving the pairing finalization request message 1701 from thereceiving terminal 308 via the communication unit 317, the seconddetermination unit 316 d of the pairing server 314 determines whether ornot a set of the pairing value and the converted address value which areincluded in the received pairing finalization request message 1701 hasbeen stored in the pairing management table 315 a. Specifically, thesecond determination unit 316 d determines whether or not the pairingvalue included in the pairing request message 1201 and the pairing valueincluded in the pairing finalization request message 1701 match, andwhether or not the communication address included in the pairing requestmessage 1201 and the communication address included in the pairingfinalization request message 1701 match.

Here, when the set of the pairing value and the converted address valuehas been stored, the processing in Step S1507 is performed next. Whenthe set of the pairing value and the converted address value has notbeen stored, the pairing server 314 transmits an error message to thereceiving terminal 308, thereby ending the processing.

(Step S1507)

The second storing unit 316 b of the pairing server 314 stores, into thepairing management table 315 a, the receiving terminal ID included inthe received pairing finalization request message 1701, in associationwith the set of the pairing value and the converted address value onwhich the determination in Step S1506 has been performed. The secondstoring unit 316 b further stores, for the phase number, “2” indicatingthe pairing finalization phase.

FIG. 18 shows an example of the pairing management table 315 a at theend of Step S1507. FIG. 18 represents that the transmitting terminal 301having the transmitting terminal ID “445566CCDD” and the receivingterminal 308 having the receiving terminal ID “778899EEFF” have beenpaired.

(Step S1508)

The pairing unit 316 e of the pairing server 314 transmits the pairingfinalization response message to the receiving terminal 308 using thecommunication unit 317. Here, a specific example of the pairingfinalization response message is described.

FIG. 19 shows an example of message data included in the pairingfinalization response message. A pairing finalization response message1901 includes, as the message data, a message identifier 1902, a version1903, and transmitting terminal ID 1904.

The message identifier 1902 is message data for identifying the messagewhich is exchanged between the pairing server 314 and the receivingterminal 308. The version 1903 is message data for identifying a versionnumber of the pairing finalization response message. The transmittingterminal ID 1904 is message data indicating the terminal ID of thetransmitting terminal 301 paired with the receiving terminal 308.

The pairing unit 316 e generates such pairing finalization responsemessage 1901. In generating the pairing finalization response message1901, the pairing unit 316 e sets “0004” indicating the pairingfinalization response message, “0100” indicating a default version, andthe terminal ID (that is “67890ABCDE” in the example of FIG. 18) of thetransmitting terminal 301 paired with the receiving terminal 308, forthe message identifier 1902, the version 1903, and the transmittingterminal ID 1904, respectively. Afterward, the communication unit 317transmits the generated pairing finalization response message 1901 tothe receiving terminal 308.

(Step S1509)

When receiving the pairing finalization response message 1901 via thecommunication unit 309, the phase management unit 310 of the receivingterminal 308 holds the transmitting terminal ID included in the receivedpairing finalization response message 1901. FIG. 20 shows an example ofdata stored in the phase management unit 310. Afterward, the phasemanagement unit 310 displays on the screen that the sharing setup hasbeen completed.

The description on processing at the pairing finalization phase endshere.

Subsequently, processing at the communication device registration phaseis described with reference to FIG. 21. The communication deviceregistration phase is performed before the pairing preparation phase andthe pairing finalization phase. The pairing preparation phase isperformed by each of (i) the transmitting mobile phone 319 and thetransmitting terminal 301 and (ii) the receiving mobile phone 323 andthe receiving terminal 308, at both of which the flow of processing isthe same. Thus, in this embodiment, the case of the receiving mobilephone 323 and the receiving terminal 308 is described as arepresentative example.

FIG. 21 is a flowchart showing a flow of processing at the communicationdevice registration phase.

(Step S2101)

The receiving mobile phone 323 transmits a communication deviceregistration start message to the receiving terminal 308 according to aninstruction of the recipient. Here, a specific example of thecommunication device registration start message is described.

FIG. 22 shows an example of message data included in the communicationdevice registration start message. A communication device registrationstart message 2201 includes, as the message data, a message identifier2202, a version 2203, and receiving mobile phone ID 2204.

The message identifier 2202 is message data for identifying the messagewhich is exchanged between the receiving mobile phone 323 and thereceiving terminal 308.

The version 2203 is message data for identifying a version number of thecommunication device registration start message.

The receiving mobile phone ID 2204 is message data indicating theterminal ID of the receiving mobile phone 323 which transmits thecommunication device registration start message. The terminal ID of themobile phone is a unique identifier assigned by a mobile-phone operator.

The receiving mobile phone 323 generates the communication deviceregistration start message 2201. The receiving mobile phone 323 sets,for example, “F001” indicating the pairing finalization start message,“0100” indicating a default version, and unique ID “EEDDCCBBAA99 . . . ”assigned by an operator, for the message identifier 2202, the version2203, and the receiving mobile phone ID 2204, respectively. Afterward,the receiving mobile phone 323 transmits the generated communicationdevice registration start message 2201 to the receiving terminal 308.

The transmission of the communication device registration start message2201 to the receiving terminal 308 is performed through the deviceconnection unit 326 of the receiving mobile phone 323 and the deviceconnection unit 312 of the receiving terminal 308.

(Step S2102)

The data conversion unit 311 of the receiving terminal 308 generates aconverted communication device value based on the terminal ID of thereceiving terminal 308 which is held in the terminal ID holding unit313, and the receiving mobile phone ID received from the receivingmobile phone 323. The converted communication device value is an outputvalue which results from input of a combined value generated bycombining the terminal ID of the receiving terminal 308 and thereceiving mobile phone ID, to the SHA-256 operational circuit in thedata conversion unit 311.

(Step S2103)

The phase management unit 306 of the receiving terminal 308 transmits acommunication device registration request message to the pairing server314. Here, a specific example of the communication device registrationrequest message is described.

FIG. 23 shows an example of message data included in the communicationdevice registration request message. A communication device registrationrequest message 2301 includes, as the message data, a message identifier2302, a version 2303, terminal ID 2304, and a converted communicationdevice value 2305.

The message identifier 2302 is message data for identifying the messagewhich is exchanged between the receiving terminal 308 and the pairingserver 314. The version 2303 is message data for identifying a versionnumber of the communication device registration request message. Theterminal ID 2304 is message data indicating the terminal ID of theterminal which transmits the communication device registration requestmessage. The converted communication device value 2305 is message dataindicating the converted communication device value generated in StepS2102.

The phase management unit 310 generates such communication deviceregistration request message 2301. In generating the communicationdevice registration request message 2301, the phase management unit 310sets, for example, “E001” indicating the communication deviceregistration request message, “0100” indicating a default version, theterminal ID to be held in the terminal ID holding unit 313, and theconverted communication device value generated in Step S2102, for themessage identifier 2302, the version 2303, the terminal ID 2304, and theconverted communication device value 2305, respectively. Afterward, thephase management unit 310 transmits the generated communication deviceregistration request message 2301 to the pairing server 314 via thecommunication unit 309.

(Step S2104)

The first determination unit 316 c of the pairing server 314 determineswhether or not a set of the terminal ID and the converted communicationdevice value which are included in the received communication devicerequest message 2301 has been stored in the communication devicemanagement table 318 a. When the set of the terminal ID and theconverted communication device value has not been stored, the processingin Step S2105 is performed next. When the set of the terminal ID and theconverted communication device value has been stored, the processing inStep S2106 is performed next.

(Step S2105)

The first storing unit 316 a of the pairing server 314 stores, into thecommunication device management table 318 a, a set of the terminal IDand the converted communication device value which are included in thereceived communication device registration request message 2301.

FIG. 24 shows an example of the communication device management table318 a at the end of Step S2105.

(Step S2106)

The pairing unit 316 e of the pairing server 314 transmits acommunication device registration response message to the receivingterminal 308 using the communication unit 317. Here, a specific exampleof the communication device registration response message is described.

FIG. 25 shows an example of message data included in the communicationdevice registration response message. A communication deviceregistration response message 2501 includes, as the message data, amessage identifier 2502, a version 2503, and a status value 2504.

The message identifier 2502 is message data for identifying the messagewhich is exchanged between the pairing server 314 and the receivingterminal 308. The version 2503 is message data for identifying a versionnumber of the communication device registration response message. Thestatus value 2504 is message data indicating a communication deviceregistration status.

The pairing unit 316 e generates such communication device registrationresponse message 2501. In generating the communication deviceregistration response message 2501, the pairing unit 316 e sets, forexample, “E002” indicating the communication device registrationresponse message, “0100” indicating a default version, and “1”indicating that the communication device has already been registeredwhen the terminal ID and the converted communication device value havealready been stored in the communication device management table 318 a,or otherwise “2” indicating that the registration of the communicationdevice has been completed, for the message identifier 2502, the version2503, and the status value 2504, respectively. Afterward, thecommunication unit 317 transmits the generated communication deviceregistration response message 2501 to the receiving terminal 308.

(Step S2107)

When receiving the communication device registration response messagevia the communication unit 309, the phase management unit 310 of thereceiving terminal 308 determines the status value included in thereceived communication device registration response message, anddisplays a result of the determination on the screen. FIG. 26 shows anexample of a display which appears upon a registration completion.

Through the above processing, the transmitting terminal 301 and thereceiving terminal 308 are paired. In this embodiment, the receivingterminal 308 is capable of obtaining the terminal ID of the transmittingterminal 301 (the transmitting terminal ID). Thus, afterward, using thetransmitting terminal ID, the receiving terminal 308 is allowed toshare, with the transmitting terminal 301, content such as photos andvideo held by the transmitting terminal 301.

It is to be noted that the transmitting terminal 301 and the receivingterminal 308 may share content in any way as long as they use the resultof pairing. For example, the pairing server 314 may control thecommunication between the transmitting terminal 301 and the receivingterminal 308 by referring to the pairing management table 315 a so as totransfer, to the receiving terminal 308, content such as photos receivedfrom the transmitting terminal 301. Furthermore, the pairing server 314may control the communication between the transmitting terminal 301 andthe receiving terminal 308 by referring to the pairing management table315 a so that content such as photos uploaded by the transmittingterminal 301 is downloadable by the receiving terminal 308.

As above, in the communication control system 300 according to thisembodiment, the transmitting terminal 301 and the receiving terminal 308are paired when the set of the pairing value and the converted addressvalue which have been transmitted from the transmitting terminal 301 tothe pairing server 314 matches, in the pairing server 314, the set ofthe pairing value and the converted address value which have beentransmitted from the receiving terminal 308 to the pairing server 314.Since a sufficiently large random number is used as the pairing value,it will not happen that the transmitting terminal is paired with anotherreceiving terminal which performs different pairing processing. In otherwords, the data transmitted from the transmitting terminal will not bereceived by a receiving terminal which is not supposed to receive thedata.

Furthermore, in the communication control system 300 according to thisembodiment, the pairing server 314 determines whether or not there ismatching of not only the pairing identifiers, but also the convertedaddress values, and therefore, it will not happen that when a maliciousrecipient who receives the shared ID from the sender transfers theshared ID to another person, and the other person inputs the transferredshared ID into the receiving terminal, the photo associated with theshared ID can be received. It is to be noted that the converted addressvalues are generated in the transmitting terminal 301 and the receivingterminal 308, but may be generated in the transmitting mobile phone 319and the receiving mobile phone 323. Furthermore, although the convertedaddress value generated by converting the address of target recipient istransmitted to the pairing server 314 in this embodiment from theperspective of privacy protection, the address of target recipient maybe transmitted to the pairing server 314 without such conversion in thecase where it can be assured that there is no privacy problem. In thiscase, the pairing server 314 determines whether or not, instead of theconverted address values, the addresses of target recipient match.

Furthermore, in the communication control system 300 according to thisembodiment, since the pairing server 314 uses the communication devicemanagement table to manage the sets of the terminal and the mobilephone, it will not happen that when a malicious recipient inputs sharedID into a receiving terminal of another person, the photo associatedwith that shared ID can be received.

Furthermore, in the communication control system 300 according to thisembodiment, the pairing value is generated by the transmitting terminal101. Thus, the transmitting terminal 301 can obtain the pairing valueimmediately when receiving the pairing start message from thetransmitting mobile phone 319. This allows the transmitting mobile phone319 to receive the pairing value in one-time communication (in oneapproaching operation) when the transmitting terminal 301 and thetransmitting mobile phone 319 communicate with each other using NFC,with the result that the convenience of the sender can improve.

Furthermore, since the pairing value is transmitted from thetransmitting terminal 301 to the receiving terminal 308 by way of themobile phones, the possibility that the receiving terminal 308 receivesan incorrect pairing value can be reduced as compared to, for example,the case where the sender tells the recipient the pairing value.

Furthermore, in the communication control system 300 according to thisembodiment, the communication address is used as the communicationdevice information that is information on the receiving mobile phone323. Thus, it is possible to reduce the occurrence of overlapping of thecommunication device information on the receiving mobile phone 323 withthe communication device information on another communication device.

Although the pairing unit 316 e transmits the pairing finalizationresponse message to the receiving terminal 308 in Step S1508 in thisembodiment, the pairing finalization response message may be transmittedto the transmitting terminal 301 or may alternatively be transmitted toboth the receiving terminal 308 and the transmitting terminal 301. Bydoing so, one or both of the transmitting terminal 301 and the receivingterminal 308 can be notified of the result of pairing.

Embodiment 2

Next, Embodiment 2 is described.

A communication control system in this embodiment is different from thecommunication control system in Embodiment 1 in the device whichgenerates the pairing value. Specifically, although the transmittingterminal 301 generates the pairing value in Embodiment 1, the pairingserver 314 generates the pairing value in this embodiment.

FIG. 27A is a block diagram showing a configuration of a communicationcontrol system 2700 in Embodiment 2. FIG. 278 is a block diagram showinga detailed configuration of the pairing server 314 in Embodiment 2. InFIGS. 27A and 27B, constituents the same as those shown in FIGS. 3A and3B in Embodiment 1 are denoted by the same numerals and are notdescribed. The block diagrams shown in FIGS. 27A and 27B are differentfrom the block diagrams shown in Embodiment 1 in that the pairing valuegeneration unit is included in the pairing server 314.

A pairing value generation unit 2701 is an operational circuit whichgenerates a pairing value that is used for pairing. In this embodiment,the pairing value generation unit 2701 corresponds to the pairingidentifier generation unit.

In this embodiment, the address management unit 322 corresponds to themanagement unit. The device connection unit 320 corresponds to the firsttransmitting unit. The communication unit 305 corresponds to the secondtransmitting unit. The communication unit 317 corresponds to the thirdtransmitting unit. The device connection unit 304 corresponds to thefourth transmitting unit. The communication unit 321 corresponds to thefifth transmitting unit. The device connection unit 326 corresponds tothe sixth transmitting unit. The communication unit 309 corresponds tothe seventh transmitting unit. The second determination unit 316 dcorresponds to the determination unit.

Next, various operations in the communication control system 2700configured as above are specifically described.

FIG. 28 is a flowchart for explaining an outline of processing of thecommunication control system 2700 in Embodiment 2. The processing of thecommunication control system 2700 includes three phases: a communicationdevice registration phase; a pairing preparation phase; and a pairingfinalization phase. As the communication registration phase, processingthe same as that described in Embodiment 1 is performed. Therefore, thedescription is not repeated.

The pairing preparation phase is processing which is performed followingthe communication device registration phase. At this pairing preparationphase, a sender transmits information necessary for pairing to arecipient by using a communication means such as SMS or MMS. Althoughthe pairing value is generated in the transmitting terminal 301 inEmbodiment 1, the pairing value is generated in the pairing server 314in this embodiment. With this, it is possible to produce the effectsdescribed in Embodiment 1 and reduce the processing load on thetransmitting terminal 301.

As the pairing finalization phase, processing the same as that describedin Embodiment 1 is performed. Therefore, the description is notrepeated.

The following describes the pairing preparation phase with reference tothe drawings.

FIGS. 29A and 29B are a flowchart showing a flow of processing at thepairing preparation phase.

(Step S2901)

Processing the same as in Step S801 in Embodiment 1 is performed.

(Steps S2902 and S2903)

Processing the same as in Steps S804 and S805 in Embodiment 1 isperformed.

(Step S2904)

The phase management unit 306 of the transmitting terminal 301 transmitsa pairing request message to the pairing server 314. Here, a specificexample of the pairing request message is described.

FIG. 30 shows an example of message data included in the pairing requestmessage. A pairing request message 3001 includes, as the message data, amessage identifier 3002, a version 3003, transmitting terminal ID 3004,a converted address value 3005, and a converted communication devicevalue 3006.

The message identifier 3002 is message data for identifying the messagewhich is exchanged between the transmitting terminal 301 and the pairingserver 314. The version 3003 is message data for identifying a versionnumber of the pairing request message. The transmitting terminal ID 3004is message data indicating the terminal ID of the transmitting terminal301 that is a terminal which transmits the pairing request message. Theconverted address value 3005 is message data indicating the convertedaddress value generated in Step S2902. The converted communicationdevice value 3006 is message data indicating the converted communicationdevice value generated in Step S2903.

The phase management unit 306 generates such pairing request message3001. In generating the pairing request message 3001, the phasemanagement unit 306 sets, for example, “0001” indicating the pairingrequest message, “0100” indicating a default version, the terminal ID tobe held in the terminal ID holding unit 307, the converted address valuegenerated in Step S2902, and the converted communication device valuegenerated in Step S2903, for the message identifier 3002, the version3003, the transmitting terminal ID 3004, the converted address value3005, and the converted communication device value 3006, respectively.Afterward, the phase management unit 306 transmits the generated pairingrequest message 3001 to the pairing server 314 via the communicationunit 305.

(Step S2905)

The first determination unit 316 c of the pairing server 314 determineswhether or not a set of the transmitting terminal ID and the convertedcommunication device value which are included in the received pairingrequest message 3001 has been stored in the communication devicemanagement table 318 a. When the set has been stored, the processingproceeds to Step S2906, and when the set has not been stored, an errormessage is transmitted to the transmitting terminal, which ends theprocessing.

(Step S2906)

The pairing value generation unit 2701 of the pairing server 314generates a pairing value. The pairing value is a random number valuewhich is sufficiently large, and is set as “123456789ABCDEF0” in thisembodiment. The pairing value may be generated after the pairing requestmessage 3001 is received and may alternatively have been generated inadvance.

(Step S2907)

The second storing unit 316 b of the pairing server 314 stores, into thepairing management table 315 a, the phase number, the pairing valuegenerated in Step S2906, the transmitting terminal ID included in thereceived pairing request message 3001, and the converted address valuein association with one another. The second storing unit 316 b stores,for the phase number, “1” indicating the pairing preparation phase.

FIG. 31 shows an example of the pairing management table 315 a at theend of Step S2907. In FIG. 31, the column for the receiving terminal IDis blank as no value has been set yet.

(Step S2908)

The pairing unit 316 e of the pairing server 314 transmits a pairingrequest response message to the transmitting terminal 301 using thecommunication unit 317. Here, a specific example of the pairing requestresponse message is described.

FIG. 32 shows an example of message data included in the pairing requestresponse message. A pairing request response message 3201 includes, asthe message data, a message identifier 3202, a version 3203, and apairing value 3204.

The message identifier 3202 is message data for identifying the messagewhich is exchanged between the pairing server 314 and the transmittingterminal 301. The version 3203 is message data for identifying a versionnumber of the pairing request response message. The pairing value 3204is message data indicating the pairing value generated in the pairingserver 314.

The pairing unit 316 e generates such pairing request response message3201. In generating the pairing request response message 3201, thepairing unit 316 e sets, for example, “0002” indicating the pairingfinalization response message, “0100” indicating a default version, andthe pairing value generated in Step S2906, for the message identifier3202, the version 3203, and the pairing value 3204, respectively.Afterward, the communication unit 317 transmits the generated pairingrequest response message 3201 to the transmitting terminal 301.

(Step S2909)

When receiving the pairing request response message 3201 via thecommunication unit 305, the phase management unit 306 of thetransmitting terminal 301 stores, in association with the phase number,the pairing value included in the received pairing finalization responsemessage. The phase management unit 306 stores, for the phase number, “1”indicating the pairing preparation phase.

(Step S2910)

A step the same as Step S803 in Embodiment 1 is performed. However, forthe pairing value 1104 that is message data in the pairing startresponse message, the pairing value included in the pairing requestresponse message received in Step S2909 is set.

(Step S2911)

After receiving the pairing start response message 1101 from thetransmitting terminal 301 in Step S2910, the transmitting mobile phone319 performs processing the same as Step S809 described in Embodiment 1.

The description on processing at the pairing preparation phase and thedescription on Embodiment 2 end here.

Through the above processing, the transmitting terminal 301 and thereceiving terminal 308 are paired. In this embodiment, the receivingterminal 308 is capable of obtaining the terminal ID of the transmittingterminal 301 (the transmitting terminal ID). Thus, afterward, using thetransmitting terminal ID, the receiving terminal 308 is allowed toshare, with the transmitting terminal 301, content such as photos andvideo held by the transmitting terminal 301.

It is to be noted that the transmitting terminal 301 and the receivingterminal 308 may share content in any way as long as they use the resultof pairing. For example, the pairing server 314 may control thecommunication between the transmitting terminal 301 and the receivingterminal 308 by referring to the pairing management table 315 a so as totransfer, to the receiving terminal 308, content such as photos receivedfrom the transmitting terminal 301. Furthermore, the pairing server 314may control the communication between the transmitting terminal 301 andthe receiving terminal 308 by referring to the pairing management table315 a so that content such as photos uploaded by the transmittingterminal 301 is downloadable by the receiving terminal 308.

As above, in the communication control system 2700 according to thisembodiment, the transmitting terminal 301 and the receiving terminal 308are paired when the set of the converted address value transmitted fromthe transmitting terminal 301 to the pairing server 314 and the pairingvalue generated in the pairing server 314 matches, in the pairing server314, the set of the pairing value and the converted address value whichhave been transmitted from the receiving terminal 308 to the pairingserver 314. Since a sufficiently large random number is used as thepairing value, it will not happen that the transmitting terminal ispaired with another receiving terminal which performs different pairingprocessing. In other words, the data transmitted from the transmittingterminal will not be received by a receiving terminal which is notsupposed to receive the data.

Furthermore, in the communication control system 2700 according to thisembodiment, the pairing server 314 determines whether or not there ismatching of not only the pairing identifiers, but also the convertedaddress values, and therefore, it will not happen that when a maliciousrecipient who receives the shared ID from the sender transfers theshared ID to another person, and the other person inputs the transferredshared ID into the receiving terminal, the photo associated with theshared ID can be received. It is to be noted that the converted addressvalues are generated in the transmitting terminal 301 and the receivingterminal 308, but may be generated in the transmitting mobile phone 319and the receiving mobile phone 323. Furthermore, although the convertedaddress value generated by converting the address of target recipient istransmitted to the pairing server 314 in this embodiment from theperspective of privacy protection, the address of target recipient maybe transmitted to the pairing server 314 without such conversion in thecase where it can be assured that there is no privacy problem. In thiscase, the pairing server 314 determines whether or not, instead of theconverted address values, the addresses of target recipient match.

Furthermore, in the communication control system 2700 according to thisembodiment, since the pairing server 314 uses the communication devicemanagement table to manage the sets of the terminal and the mobilephone, it will not happen that when a malicious recipient inputs sharedID into a receiving terminal of another person, the photo associatedwith that shared ID can be received.

Embodiment 3

Next, Embodiment 3 is described.

A communication control system in this embodiment is different from thecommunication control system in Embodiment 1 in the device whichgenerates the pairing value. Specifically, although the transmittingterminal 301 generates the pairing value in Embodiment 1, thetransmitting mobile phone 319 generates the pairing value in thisembodiment.

FIG. 33A is a block diagram showing a configuration of a communicationcontrol system 3300 in Embodiment 3. FIG. 33B is a block diagram showinga detailed configuration of the pairing server 314 in Embodiment 3. InFIGS. 33A and 33B, constituents the same as those shown in FIGS. 3A and3B in Embodiment 1 are denoted by the same numerals and are notdescribed. The block diagrams shown in FIGS. 33A and 33B are differentfrom the block diagrams shown in Embodiment 1 in that the pairing valuegeneration unit is included in the transmitting mobile phone 319.

A pairing value generation unit 3301 is an operational circuit whichgenerates a pairing value that is used for pairing. In this embodiment,the pairing value generation unit 3301 corresponds to the pairingidentifier generation unit.

In this embodiment, the address management unit 322 corresponds to themanagement unit. The device connection unit 320 corresponds to the firsttransmitting unit. The communication unit 305 corresponds to the secondtransmitting unit. The device connection unit 304 corresponds to thethird transmitting unit. The communication unit 321 corresponds to thefourth transmitting unit. The device connection unit 326 corresponds tothe fifth transmitting unit. The communication unit 309 corresponds tothe sixth transmitting unit. The second determination unit 316 dcorresponds to the determination unit.

Next, various operations in the communication control system 3300configured as above are specifically described.

FIG. 34 is a flowchart for explaining an outline of processing of thecommunication control system 3300 in Embodiment 3. The processing of thecommunication control system 3300 includes three phases: a communicationdevice registration phase; a pairing preparation phase; and a pairingfinalization phase. As the communication registration phase, processingthe same as that described in Embodiment 1 is performed. Therefore, thedescription is not repeated.

The pairing preparation phase is processing which is performed followingthe communication device registration phase. At this pairing preparationphase, a sender transmits information necessary for pairing to arecipient by using a communication means such as SMS or MMS. Althoughthe pairing value is generated in the transmitting terminal 301 inEmbodiment 1, the pairing value is generated in the transmitting mobilephone 319 in this embodiment. With this, it is possible to produce theeffects described in Embodiment 1 and reduce the processing load on thetransmitting terminal 301.

As the pairing finalization phase, processing the same as that describedin Embodiment 1 is performed. Therefore, the description is notrepeated.

The following describes the pairing preparation phase with reference tothe drawings.

FIGS. 35A and 35B are a flowchart showing a flow of processing at thepairing preparation phase.

(Step S3501)

According to an instruction of a sender, the transmitting mobile phone319 transmits a pairing start message to the transmitting terminal 301.Here, a specific example of the pairing start message is described.

FIG. 36 shows an example of message data included in the pairing startmessage. A pairing start message 3601 includes, as the message data, amessage identifier 3602, a version 3603, transmitting mobile phone ID3604, a sender address 3605, an address of target recipient 3606, and apairing value 3607.

The message identifier 3602 is message data for identifying the messagewhich is exchanged between the transmitting mobile phone 319 and thetransmitting terminal 301.

The version 3603 is message data for identifying a version number of thepairing start message. When the message data included in the messagehave any change such as addition or deletion due to system expansion,the version number is increased. Each of the mobile phone and theterminal compares a value of the version number included in the messagewith the version number which the device itself supports, to therebydetermine whether to be able to handle the message.

The transmitting mobile phone ID 3604 is message data indicating theterminal ID of the transmitting mobile phone 319 which transmits thepairing start message. The terminal ID of the mobile phone is a uniqueidentifier assigned by a mobile-phone operator.

The sender address 3605 is address data which the sender uses in SMS,MMS, or the like, and is stored in the address management unit 322 ofthe transmitting mobile phone 319.

The address of target recipient 3606 is address data of SMS, MMS, or thelike which indicate a recipient with whom the sender wishes to sharephotos, etc., and is stored in the address management unit 322 of thetransmitting mobile phone 319.

The pairing value 3607 is message data indicating the pairing valuewhich is generated in the transmitting mobile phone 319.

The sender selects a menu “sharing setting (send)” on the menu screen ofthe transmitting mobile phone 319. Upon selection of the menu “sharingsetting (send)”, the transmitting mobile phone 319 displays, on thescreen, the address data stored in the address management unit 322. FIG.10 shows a display example of the address data. The sender selects thetarget recipient with whom the sender wishes to share photos, etc., fromamong the addresses displayed on the screen.

Upon selection of the target recipient, the pairing value generationunit 3301 of the transmitting mobile phone 319 generates a pairingvalue. The pairing value is a random number value which is sufficientlylarge, and is set as “123456789ABCDEF0” in this embodiment. The pairingvalue may be generated after the pairing start message 901 is receivedand may alternatively have been generated in advance.

Afterward, the transmitting mobile phone 319 generates the pairing startmessage 3601. The transmitting mobile phone 319 sets, for example,“1001” indicating the pairing start message, “0100” indicating a defaultversion, unique ID “FFEEDDCCBBAA . . . ” assigned by an operator, an MMSaddress of the sender “suzukixxx.ne.jp”, an MMS address of the targetrecipient “yamamotoxxx.ne.jp”, and the pairing value “123456789ABCDEF0”generated in the pairing value generation unit 3301, for the messageidentifier 3602, the version 3603, the transmitting mobile phone ID3604, the sender address 3605, the address of target recipient 3606, andthe pairing value 3607, respectively. Afterward, the transmitting mobilephone 319 transmits the generated pairing start message 3601 to thetransmitting terminal 301.

The transmission of the pairing start message 3601 to the transmittingterminal 301 is performed through the device connection unit 320 of thetransmitting mobile phone 319 and the device connection unit 304 of thetransmitting terminal 301.

(Step S3502)

The phase management unit 306 of the transmitting terminal 301 stores,in association with the phase number, the pairing value included in thepairing start message 3601 received from the transmitting mobile phone319. The phase management unit 306 stores, for the phase number, “1”indicating the pairing preparation phase.

(Steps S3503 and S3504)

Processing the same as in Steps S804 and S805 in Embodiment 1 isperformed.

(Step S3505)

Processing the same as in Step S806 in Embodiment 1 is performed.However, for the pairing value 1205 that is message data in the pairingrequest message, the pairing value included in the pairing start messagereceived in Step S3502 is set.

(Steps S3506 and S3507)

Processing the same as in Steps S807 and S808 in Embodiment 1 isperformed.

(Step S3508)

After transmitting the pairing start message 3601 to the transmittingterminal 301 in Step S3501, the transmitting mobile phone 319 displays asend screen for an MMS message which is directed to the target recipientdesignated in Step S3501 by the sender on the menu “sharing setting(send)”, and accepts a message input from the sender. FIG. 14 shows ascreen example which appears after the message input.

After completion of the message input from the sender, the transmittingmobile phone 319 transmits an MMS message to the target recipientdesignated in Step S3501 by the sender. At this time, the pairing valuegenerated in Step S3501 is attached to the MMS message to betransmitted.

The description on processing at the pairing preparation phase and thedescription on Embodiment 3 end here.

Through the above processing, the transmitting terminal 301 and thereceiving terminal 308 are paired. In this embodiment, the receivingterminal 308 is capable of obtaining the terminal ID of the transmittingterminal 301 (the transmitting terminal ID). Thus, afterward, using thetransmitting terminal ID, the receiving terminal 308 is allowed toshare, with the transmitting terminal 301, content such as photos andvideo held by the transmitting terminal 301.

It is to be noted that the transmitting terminal 301 and the receivingterminal 308 may share content in any way as long as they use the resultof pairing. For example, the pairing server 314 may control thecommunication between the transmitting terminal 301 and the receivingterminal 308 by referring to the pairing management table 315 a so as totransfer, to the receiving terminal 308, content such as photos receivedfrom the transmitting terminal 301. Furthermore, the pairing server 314may control the communication between the transmitting terminal 301 andthe receiving terminal 308 by referring to the pairing management table315 a so that content such as photos uploaded by the transmittingterminal 301 is downloadable by the receiving terminal 308.

As above, in the communication control system 3300 according to thisembodiment, the transmitting terminal 301 and the receiving terminal 308are paired when the set of the converted address value transmitted fromthe transmitting terminal 301 to the pairing server 314 and the pairingvalue generated in the transmitting mobile phone 319 matches, in thepairing server 314, the set of the pairing value and the convertedaddress value which have been transmitted from the receiving terminal308 to the pairing server 314. Since a sufficiently large random numberis used as the pairing value, it will not happen that the transmittingterminal is paired with another receiving terminal which performsdifferent pairing processing. In other words, the data transmitted fromthe transmitting terminal will not be received by a receiving terminalwhich is not supposed to receive the data.

Furthermore, in the communication control system 3300 according to thisembodiment, the pairing server 314 determines whether or not there ismatching of not only the pairing identifiers, but also the convertedaddress values, and therefore, it will not happen that when a maliciousrecipient who receives the shared ID from the sender transfers theshared ID to another person, and the other person inputs the transferredshared ID into the receiving terminal, the photo associated with theshared ID can be received. It is to be noted that the converted addressvalues are generated in the transmitting terminal 301 and the receivingterminal 308, but may be generated in the transmitting mobile phone 319and the receiving mobile phone 323. Furthermore, although the convertedaddress value generated by converting the address of target recipient istransmitted to the pairing server 314 in this embodiment from theperspective of privacy protection, the address of target recipient maybe transmitted to the pairing server 314 without such conversion in thecase where it can be assured that there is no privacy problem. In thiscase, the pairing server 314 determines whether or not, instead of theconverted address values, the addresses of target recipient match.

Furthermore, in the communication control system 3300 according to thisembodiment, since the pairing server 314 uses the communication devicemanagement table to manage the sets of the terminal and the mobilephone, it will not happen that when a malicious recipient inputs sharedID into a receiving terminal of another person, the photo associatedwith that shared ID can be received.

Embodiment 4

Next, Embodiment 4 is described.

A communication control system in this embodiment is different from thecommunication control system in Embodiment 1 in the device whichdetermines whether or not the addresses match. Specifically, althoughthe pairing server 314 determines whether or not the addresses match inEmbodiment 1, the receiving terminal 308 determines whether or not theaddresses match in this embodiment.

FIG. 37A is a block diagram showing a configuration of a communicationcontrol system 3700 in Embodiment 4. FIG. 37B is a block diagram showinga detailed configuration of the pairing server 314 in Embodiment 4. InFIGS. 37A and 37B, constituents the same as those shown in FIGS. 3A and3B in Embodiment 1 are denoted by the same numerals and are notdescribed. The block diagrams in FIGS. 37A and 37B are different fromthe block diagrams in Embodiment 1 in that the receiving terminal 308includes a determination unit 3701 which performs comparison anddetermination on the converted address values.

The determination unit 3701 is an operational circuit which performscomparison and determination on the converted address values. Detailswill be described later. In this embodiment, the determination unit 3701corresponds to the first determination unit.

In this embodiment, the address management unit 322 corresponds to themanagement unit. The device connection unit 320 corresponds to the firsttransmitting unit. The pairing value generation unit 303 corresponds tothe pairing identifier generation unit. The data conversion unit 302corresponds to the first conversion unit. The communication unit 305corresponds to the second transmitting unit. The device connection unit304 corresponds to the third transmitting unit. The communication unit321 corresponds to the fourth transmitting unit. The device connectionunit 326 corresponds to the fifth transmitting unit. The data conversionunit 311 corresponds to the second conversion unit. The communicationunit 309 corresponds to the sixth transmitting unit.

Next, various operations in the communication control system 3700configured as above are specifically described.

FIG. 38 is a flowchart for explaining an outline of processing of thecommunication control system 3700 in Embodiment 4. The processing of thecommunication control system 3700 includes three phases: a communicationdevice registration phase; a pairing preparation phase; and a pairingfinalization phase. As the communication registration phase, processingthe same as that described in Embodiment 1 is performed. Therefore, thedescription is not repeated.

The pairing preparation phase is processing which is performed followingthe communication device registration phase. At this pairing preparationphase, a sender transmits information necessary for pairing to arecipient by using a communication means such as SMS or MMS.

The pairing finalization phase is processing which is performedfollowing the pairing preparation phase. At this pairing finalizationphase, pairing is finalized using the information necessary for pairingwhich the recipient received from the sender.

Although the pairing server performs comparison and determination on theconverted address value received from the transmitting terminal and theconverted address value received from the receiving terminal inEmbodiment 1, the receiving terminal performs comparison anddetermination on the converted address value resulting from conversionin the transmitting terminal and the converted address value resultingfrom conversion in the receiving mobile phone in this embodiment. Withthis, it is possible to produce the effects described in Embodiment 1and reduce the processing load on the pairing server.

The following describes the pairing preparation phase and the pairingfinalization phase in this order with reference to the drawings.

FIGS. 39A and 39B are a flowchart showing a flow of processing at thepairing preparation phase.

(Steps S3901 and S3902)

Processing the same as in Steps S801 and S802 in Embodiment 1 isperformed.

(Step S3903)

Processing the same as in Step S804 in Embodiment 1 is performed.

(Step S3904)

The phase management unit 306 of the transmitting terminal 301 transmitsa pairing start response message to the transmitting mobile phone 319.Here, a specific example of the pairing start response message isdescribed.

FIG. 40 shows an example of message data included in the pairing startresponse message. A pairing start response message 4001 includes, as themessage data, a message identifier 4002, a version 4003, a pairing value4004, and a converted address value 4005.

The message identifier 4002 is message data for identifying the messagewhich is exchanged between the transmitting mobile phone 319 and thetransmitting terminal 301. The version 4003 is message data foridentifying a version number of the pairing start response message. Thepairing value 4004 is message data indicating the pairing valuegenerated in Step S3902. The converted address value 4005 is a convertedvalue of target recipient address generated in Step S3903.

The phase management unit 316 generates such pairing start responsemessage 4001. In generating the pairing start response message 4001, thephase management unit 316 sets, for example, “1002” indicating thepairing start response message, “0100” indicating a default version, thepairing value “123456789ABCDEF0” generated in Step S3902, and theconverted address value generated in Step S3903, for the messageidentifier 4002, the version 4003, the pairing value 4004, and theconverted address value 4005, respectively.

The transmission of the pairing start response message 4001 to thetransmitting mobile phone 319 is performed through the device connectionunit 304 of the transmitting terminal 301 and the device connection unit320 of the transmitting mobile phone 319.

(Step S3905)

Processing the same as in Step S805 in Embodiment 1 is performed.

(Step S3906)

The phase management unit 306 of the transmitting terminal 301 transmitsa pairing request message to the pairing server 314. Here, a specificexample of the pairing request message is described.

FIG. 41 shows an example of message data included in the pairing requestmessage. A pairing request message 4101 includes, as the message data, amessage identifier 4102, a version 4103, transmitting terminal ID 4104,a pairing value 4105, and a converted communication device value 4106.

The message identifier 4102 is message data for identifying the messagewhich is exchanged between the transmitting terminal 301 and the pairingserver 314. The version 4103 is message data for identifying a versionnumber of the pairing request message. The transmitting terminal ID 4104is message data indicating the terminal ID of the transmitting terminal301 that is a terminal which transmits the pairing request message. Thepairing value 4105 is message data indicating the pairing valuegenerated in Step S3902. The converted communication device value 4106is message data indicating the converted communication device valuegenerated in Step S3905.

The phase management unit 306 generates such pairing request message4101. In generating the pairing request message 4101, the phasemanagement unit 306 sets, for example, “0001” indicating the pairingrequest message, “0100” indicating a default version, the terminal ID tobe held in the terminal ID holding unit 307, the pairing value generatedin Step S3902, and the converted communication device value generated inStep S3905, for the message identifier 4102, the version 4103, thetransmitting terminal ID 4104, the pairing value 4105, and the convertedcommunication device value 4106, respectively. Afterward, the phasemanagement unit 306 transmits the generated pairing request message 4101to the pairing server 314 via the communication unit 305.

(Step S3907)

Processing the same as in Step S807 in Embodiment 1 is performed.

(Step S3908)

When receiving the pairing request message 4101 from the transmittingterminal 301 via the communication unit 317, the second storing unit 316b of the pairing server 314 stores, into the pairing management table315 a, the phase number, the transmitting terminal ID included in thereceived pairing request message 4101, and the pairing value inassociation with one another. The second storing unit 316 b stores, forthe phase number, “1” indicating the pairing preparation phase.

FIG. 42 shows an example of the pairing management table 315 a at theend of Step S3908. In FIG. 42, since the converted address value is notused in the pairing server 314, the column for the receiving terminal IDis blank as no value has been set yet.

(Step S3909)

After receiving the pairing start response message 4001 from thetransmitting terminal 301 in Step S3904, the transmitting mobile phone319 displays a send screen for an MMS message which is directed to thetarget recipient designated by the sender on the menu “sharing setting(send)” in Step S3901, and accepts a message input from the sender. FIG.14 shows a screen example which appears after the message input.

After completion of the message input from the sender, the transmittingmobile phone 319 transmits an MMS message to the target recipientdesignated in Step S3901 by the sender. At this time, the pairing valueand the converted address value which are included in the pairing startresponse message received from the transmitting terminal 301 in StepS3904 are attached to the MMS message to be transmitted.

The description on processing at the pairing preparation phase endshere.

Subsequently, processing at the pairing finalization phase is describedwith reference to FIGS. 43A and 43B.

FIGS. 43A and 43B are a flowchart showing a flow of processing at thepairing finalization phase.

(Step S4301)

The recipient receives the MMS message from the sender. Afterward, thereceiving mobile phone 323 transmits a pairing finalization startmessage to the receiving terminal 308 according to an instruction of therecipient. Here, a specific example of the pairing finalization startmessage is described.

FIG. 44 shows an example of message data included in the pairingfinalization start message. A pairing finalization start message 4401includes, as the message data, a message identifier 4402, a version4403, receiving mobile phone ID 4404, a sender address 4405, a pairingvalue 4406, and a converted address value 4407.

The message identifier 4402 is message data for identifying the messagewhich is exchanged between the receiving mobile phone 323 and thereceiving terminal 308.

The version 4403 is message data for identifying a version number of thepairing finalization start message.

The receiving mobile phone ID 4404 is message data indicating theterminal ID of the receiving mobile phone 323 which transmits thepairing finalization start message. The terminal ID of the mobile phoneis a unique identifier assigned by a mobile-phone operator.

The recipient address 4405 is address data which the recipient uses inSMS, MMS, or the like, and is stored in the address management unit 324of the receiving mobile phone 323.

The pairing value 4406 is message data indicating the pairing valuereceived from the transmitting mobile phone 319.

The converted address value 4407 is message data indicating theconverted address value received from the transmitting mobile phone 319.

The receiving mobile phone 323 generates the pairing finalization startmessage 4401 according to an instruction of the recipient. The receivingmobile phone 323 sets, for example, “1003” indicating the pairingfinalization start message, “0100” indicating a default version, uniqueID “EEDDCCBBAA99 . . . ” assigned by an operator, an MMS address of therecipient “yamamotoxxx.ne.jp”, the pairing value attached to the MMSmessage received from the sender, and the converted address valuereceived from the transmitting mobile phone 319, for the messageidentifier 4402, the version 4403, the receiving mobile phone ID 4404,the recipient address 4405, the pairing value 4406, and the convertedaddress value 4407, respectively. Afterward, the receiving mobile phone323 transmits the generated pairing finalization start message 4401 tothe receiving terminal 308.

The transmission of the pairing finalization start message 4401 to thereceiving terminal 308 is performed through the device connection unit326 of the receiving mobile phone 323 and the device connection unit 312of the receiving terminal 308.

(Steps S4302 and S4303)

Processing the same as in Steps S1502 and S1503 in Embodiment 1 isperformed.

(Step S4304)

The determination unit 3701 of the receiving terminal 308 compares theconverted address value included in the pairing finalization startmessage 4401 received from the receiving mobile phone 323 in Step S4301with the converted address value generated in Step S4302. Specifically,the determination unit 3701 determines whether or not there is matchingof two converted address values: the converted address value generatedby converting the address held in the transmitting mobile phone 319; andthe converted address value generated by converting the addresspreviously held in the receiving mobile phone 323. As a result of thecomparison, when the two converted address values match, processing inStep S4305 is performed. On the other hand, when the two convertedaddress values do not match, the receiving terminal 308 displays anerror message, thereby ending the processing. In other words, when thetwo converted address values do not match, the processing in Step S4305is not performed.

(Step S4305)

The phase management unit 306 of the receiving terminal 308 stores, inassociation with the phase number, the pairing value included in thereceived pairing finalization start message 4401. The phase managementunit 306 stores, for the phase number, “1” indicating the pairingpreparation phase. Afterward, the communication unit 309 transmits apairing finalization request message to the pairing server 314. Here, aspecific example of the pairing finalization request message isdescribed.

FIG. 45 shows an example of message data included in the pairingfinalization request message. A pairing finalization request message4501 includes, as the message data, a message identifier 4502, a version4503, receiving terminal ID 4504, a pairing value 4505, and a convertedcommunication device value 4506.

The message identifier 4502 is message data for identifying the messagewhich is exchanged between the receiving terminal 308 and the pairingserver 314. The version 4503 is message data for identifying a versionnumber of the pairing finalization request message. The receivingterminal ID 4504 is message data indicating the terminal ID of thereceiving terminal 308 that is a terminal which transmits the pairingfinalization request message. The pairing value 4505 is message dataindicating the pairing value received from the receiving mobile phone323. The converted communication device value 4506 is message dataindicating the converted communication device value generated in StepS4303.

The phase management unit 310 generates such pairing finalizationrequest message 4501. In generating the pairing finalization requestmessage 4501, the phase management unit 310 sets, for example, “0003”indicating the pairing finalization request message, “0100” indicating adefault version, the terminal ID to be held in the terminal ID holdingunit 313, the pairing value received from the receiving mobile phone323, and the converted communication device value generated in StepS4303, for the message identifier 4502, the version 4503, the receivingterminal ID 4504, the pairing value 4505, and the convertedcommunication device value 4506, respectively. Afterward, the phasemanagement unit 310 transmits the generated pairing finalization requestmessage 4501 to the pairing server 314 via the communication unit 309.

(Step S4306)

Processing the same as in Step S1505 in Embodiment 1 is performed.

(Step S4307)

When receiving the pairing finalization request message 4501 from thereceiving terminal 308 via the communication unit 317, the seconddetermination unit 316 d of the pairing server 314 determines whether ornot the pairing value included in the received pairing finalizationrequest message 4501 has been stored in the pairing management table 315a. Here, when the pairing value has been stored, the processing in StepS4308 is performed next. When the pairing value has not been stored, thepairing server 314 transmits an error message to the receiving terminal308, thereby ending the processing.

(Step S4308)

The second storing unit 316 b of the pairing server 314 stores, into thepairing management table 315 a, the receiving terminal ID included inthe received pairing finalization request message 4501, in associationwith the pairing value on which the determination in Step S4307 has beenperformed. The second storing unit 316 b stores, for the phase number,“2” indicating the pairing finalization phase.

FIG. 46 shows an example of the pairing management table 315 a at theend of Step S4308. FIG. 46 represents that the transmitting terminal 301having the transmitting terminal ID “445566CCDD” and the receivingterminal 308 having the receiving terminal ID “778899EEFF” have beenpaired.

(Steps S4309 and S4310)

Processing the same as in Steps S1508 and S1509 in Embodiment 1 isperformed.

The description on processing in the pairing finalization phase endshere.

Through the above processing, the transmitting terminal 301 and thereceiving terminal 308 are paired. In this embodiment, the receivingterminal 308 is capable of obtaining the terminal ID of the transmittingterminal 301 (the transmitting terminal ID). Thus, afterward, using thetransmitting terminal ID, the receiving terminal 308 is allowed toshare, with the transmitting terminal 301, content such as photos andvideo held by the transmitting terminal 301.

It is to be noted that the transmitting terminal 301 and the receivingterminal 308 may share content in any way as long as they use the resultof pairing. For example, the pairing server 314 may control thecommunication between the transmitting terminal 301 and the receivingterminal 308 by referring to the pairing management table 315 a so as totransfer, to the receiving terminal 308, content such as photos receivedfrom the transmitting terminal 301. Furthermore, the pairing server 314may control the communication between the transmitting terminal 301 andthe receiving terminal 308 by referring to the pairing management table315 a so that content such as photos uploaded by the transmittingterminal 301 is downloadable by the receiving terminal 308.

As above, in the communication control system 3700 according to thisembodiment, the transmitting terminal 301 and the receiving terminal 308are paired when the pairing value transmitted from the transmittingterminal 301 to the pairing server 314 matches, in the pairing server314, the pairing value transmitted from the receiving terminal 308 tothe pairing server 314. Since a sufficiently large random number is usedas the pairing value, it will not happen that the transmitting terminalis paired with another receiving terminal which performs differentpairing processing. In other words, the data transmitted from thetransmitting terminal will not be received by a receiving terminal whichis not supposed to receive the data.

Furthermore, in the communication control system 3700 according to thisembodiment, the receiving terminal 308 determines whether or not theconverted address values match, and therefore, it will not happen thatwhen a malicious recipient who receives the shared ID from the sendertransfers the shared ID to another person, and the other person inputsthe transferred shared ID into the receiving terminal, the photoassociated with the shared ID can be received.

Furthermore, in the communication control system 3700 according to thisembodiment, since the pairing server 314 uses the communication devicemanagement table to manage the sets of the terminal and the mobilephone, it will not happen that when a malicious recipient inputs sharedID into a receiving terminal of another person, the photo associatedwith that shared ID can be received.

Embodiment 5

Next, Embodiment 5 is described.

A communication control system in this embodiment is different from thecommunication control system in Embodiment 4 in the device whichdetermines whether or not the addresses match. Specifically, althoughthe receiving terminal 308 determines whether or not the addresses matchin Embodiment 4, the receiving mobile phone 323 determines whether ornot the addresses match in this embodiment.

FIG. 47A is a block diagram showing a configuration of a communicationcontrol system 4700 in Embodiment 5. FIG. 47B is a block diagram showinga detailed configuration of the pairing server 314 in Embodiment 5. InFIGS. 47A and 47B, constituents the same as those shown in FIGS. 37A and37B in Embodiment 4 are denoted by the same numerals and are notdescribed. The block diagrams in FIGS. 47A and 47B are different fromthe block diagrams in Embodiment 4 in that the receiving mobile phone323 includes a determination unit 4703 which performs comparison anddetermination on the converted address values.

Data conversion units 4701 and 4702 are each an operational circuitwhich converts data, such as addresses of mobile phone emails, using aone-way function. In this embodiment, the data conversion unit 4701corresponds to the first conversion unit, and the data conversion unit4702 corresponds to the second conversion unit.

The determination unit 4703 is an operational circuit which performscomparison and determination on the converted address values. In thisembodiment, the determination unit 4703 corresponds to the firstdetermination unit. Details will be described later.

In this embodiment, the pairing value generation unit 303 corresponds tothe pairing identifier generation unit. The communication unit 305corresponds to the first transmitting unit. The device connection unit304 corresponds to the second transmitting unit. The address managementunit 322 corresponds to the management unit. The communication unit 321corresponds to the third transmitting unit. The device connection unit326 corresponds to the fourth transmitting unit. The communication unit309 corresponds to the fifth transmitting unit.

Next, various operations in the communication control system 4700configured as above are specifically described.

FIG. 48 is a flowchart for explaining an outline of processing of thecommunication control system 4700 in Embodiment 5. The processing of thecommunication control system 4700 includes three phases: a communicationdevice registration phase; a pairing preparation phase; and a pairingfinalization phase. As the communication registration phase, processingthe same as that described in Embodiment 1 is performed. Therefore, thedescription is not repeated.

The pairing preparation phase is processing which is performed followingthe communication device registration phase. At this pairing preparationphase, a sender transmits information necessary for pairing to arecipient by using a communication means such as SMS or MMS.

The pairing finalization phase is processing which is performedfollowing the pairing preparation phase. At this pairing finalizationphase, pairing is finalized using the information necessary for pairingwhich the recipient received from the sender.

Although the receiving terminal performs comparison and determination onthe converted address value resulting from conversion in thetransmitting terminal and the converted address value resulting fromconversion in the receiving mobile phone in Embodiment 4, the receivingmobile phone performs comparison and determination on the convertedaddress value resulting from conversion in the transmitting mobile phoneand the converted address value resulting from conversion in thereceiving mobile phone in this embodiment. With this, it is possible toproduce the effects described in Embodiment 4 and reduce the processingload on the receiving terminal.

The following describes the pairing preparation phase and the pairingfinalization phase in this order with reference to the drawings.

FIGS. 49A and 49B are a flowchart showing a flow of processing at thepairing preparation phase.

(Step S4901)

According to an instruction of a sender, the transmitting mobile phone319 transmits a pairing start message to the transmitting terminal 301.Here, a specific example of the pairing start message is described.

FIG. 50 shows an example of message data included in the pairing startmessage. A pairing start message 5001 includes, as the message data, amessage identifier 5002, a version 5003, transmitting mobile phone ID5004, and a sender address 5005.

The message identifier 5002 is message data for identifying the messagewhich is exchanged between the transmitting mobile phone 319 and thetransmitting terminal 301.

The version 5003 is message data for identifying a version number of thepairing start message. When the message data included in the messagehave any change such as addition or deletion due to system expansion,the version number is increased. Each of the mobile phone and theterminal compares a value of the version number included in the messagewith the version number which the device itself supports, to therebydetermine whether to be able to handle the message.

The transmitting mobile phone ID 5004 is message data indicating theterminal ID of the transmitting mobile phone 319 which transmits thepairing start message. The terminal ID of the mobile phone is a uniqueidentifier assigned by a mobile-phone operator.

The sender address 5005 is address data which the sender uses in SMS,MMS, or the like, and is stored in the address management unit 322 ofthe transmitting mobile phone 319.

The sender selects a menu “sharing setting (send)” on the menu screen ofthe transmitting mobile phone 319. Upon selection of the menu “sharingsetting (send)”, the transmitting mobile phone 319 displays, on thescreen, the address data stored in the address management unit 322. FIG.10 shows a display example of the address data. The sender selects thetarget recipient with whom the sender wishes to share photos, etc., fromamong the addresses displayed on the screen.

Upon selection of the target recipient, the transmitting mobile phone319 generates the pairing start message 5001. The transmitting mobilephone 319 sets, for example, “1001” indicating the pairing startmessage, “0100” indicating a default version, unique ID “FFEEDDCCBBAA .. . ” assigned by an operator, and an MMS address of the sender“suzukixxx.ne.jp”, for the message identifier 5002, the version 5003,the transmitting mobile phone ID 5004, and the sender address 5005,respectively. Afterward, the transmitting mobile phone 319 transmits thegenerated pairing start message 5001 to the transmitting terminal 301.

The transmission of the pairing start message 5001 to the transmittingterminal 301 is performed through the device connection unit 320 of thetransmitting mobile phone 319 and the device connection unit 304 of thetransmitting terminal 301.

(Step S4902)

Processing the same as in Step S3902 in Embodiment 4 (Step S802 inEmbodiment 1) is performed.

(Step S4903)

The phase management unit 306 of the transmitting terminal 301 transmitsa pairing start response message to the transmitting mobile phone 319.Here, a specific example of the pairing start response message isdescribed.

FIG. 51 shows an example of message data included in the pairing startresponse message. A pairing start response message 5101 includes, as themessage data, a message identifier 5102, a version 5103, and a pairingvalue 5104.

The message identifier 5102 is message data for identifying the messagewhich is exchanged between the transmitting mobile phone 319 and thetransmitting terminal 301. The version 5103 is message data foridentifying a version number of the pairing start response message. Thepairing value 5104 is message data indicating the pairing valuegenerated in Step S4902.

The phase management unit 316 generates such pairing start responsemessage 5101. In generating the pairing start response message 4001, thephase management unit 316 sets, for example, “1002” indicating thepairing start response message, “0100” indicating a default version, andthe pairing value “123456789ABCDEF0” generated in Step S4902, for themessage identifier 5102, the version 5103, and the pairing value 5104,respectively.

The transmission of the pairing start response message 5101 to thetransmitting mobile phone 319 is performed through the device connectionunit 304 of the transmitting terminal 301 and the device connection unit320 of the transmitting mobile phone 319.

(Step S4904)

Processing the same as in Step S3905 in Embodiment 4 (Step S805 inEmbodiment 1) is performed.

(Step S4905)

Processing the same as in Step S3906 in Embodiment 4 is performed.

(Step S4906)

Processing the same as in Step S3907 in Embodiment 4 (Step S807 inEmbodiment 1) is performed.

(Step S4907)

Processing the same as in Step S3908 in Embodiment 4 is performed.

(Step S4908)

The data conversion unit 4701 of the transmitting mobile phone 319generates the converted address value based on the address of targetrecipient (an MMS address of the target recipient) selected in StepS4901 by the sender. In this embodiment, the converted address value isan output value which results from input of the address of targetrecipient to an SHA-256 operational circuit in the data conversion unit4701.

(Step S4909)

After receiving the pairing start response message 5101 from thetransmitting terminal 301 in Step S4903, the transmitting mobile phone319 displays a send screen for an MMS message which is directed to thetarget recipient designated by the sender on the menu “sharing setting(send)” in Step S4901, and accepts a message input from the sender. FIG.14 shows a screen example which appears after the message input.

After completion of the message input from the sender, the transmittingmobile phone 319 transmits an MMS message to the target recipientdesignated in Step S4901 by the sender. At this time, the pairing valueand the converted address value which are included in the pairing startresponse message received from the transmitting terminal 301 in StepS4903 are attached to the MMS message to be transmitted.

The description on processing at the pairing preparation phase endshere.

Subsequently, processing at the pairing finalization phase is describedwith reference to FIGS. 52A and 52B.

FIGS. 52A and 52B are a flowchart showing a flow of processing at thepairing finalization phase.

(Step S5201)

The recipient receives the MMS message from the sender. Afterward, thedata conversion unit 4702 of the receiving mobile phone 323 generatesthe converted address value based on the recipient email address held inthe address management unit 324. In this embodiment, the convertedaddress value is an output value which results from input of therecipient email address to an SHA-256 operational circuit in the dataconversion unit 4702.

(Step S5202)

The determination unit 4703 of the receiving mobile phone 323 comparesthe converted address value included in the MMS message received fromthe sender in Step S5201 with the converted address value generated inStep S5201. As a result of the comparison, processing in Step S5203 isperformed when the two converted address values match. On the otherhand, when the two converted address values do not match, the receivingmobile phone 323 displays an error message, thereby ending theprocessing. In other words, when the two converted address values do notmatch, the processing in Step S5203 is not performed.

(Step S5203)

The receiving mobile phone 323 transmits a pairing finalization startmessage to the receiving terminal 308 according to an instruction of therecipient. Here, a specific example of the pairing finalization startmessage is described.

FIG. 53 shows an example of message data included in the pairingfinalization start message. A pairing finalization start message 5301includes, as the message data, a message identifier 5302, a version5303, receiving mobile phone ID 5304, and a pairing value 5305.

The message identifier 5302 is message data for identifying the messagewhich is exchanged between the receiving mobile phone 323 and thereceiving terminal 308.

The version 5303 is message data for identifying a version number of thepairing finalization start message.

The receiving mobile phone ID 5304 is message data indicating theterminal ID of the receiving mobile phone 323 which transmits thepairing finalization start message. The terminal ID of the mobile phoneis a unique identifier assigned by a mobile-phone operator.

The pairing value 5305 is message data indicating the pairing valuereceived from the transmitting mobile phone 319.

The receiving mobile phone 323 generates the pairing finalization startmessage 5301 according to an instruction of the recipient. The receivingmobile phone 323 sets, for example, “1003” indicating the pairingfinalization start message, “0100” indicating a default version, uniqueID “EEDDCCBBAA99 . . . ” assigned by an operator, and the pairing valueattached to the MMS message received from the sender, for the messageidentifier 5302, the version 5303, the receiving mobile phone ID 5304,and the pairing value 5305, respectively. Afterward, the receivingmobile phone 323 transmits the generated pairing finalization startmessage 5301 to the receiving terminal 308.

The transmission of the pairing finalization start message 5301 to thereceiving terminal 308 is performed through the device connection unit326 of the receiving mobile phone 323 and the device connection unit 312of the receiving terminal 308.

(Step S5204)

Processing the same as in Step S4303 in Embodiment 4 (Step S1503 inEmbodiment 1) is performed.

(Step S5205)

The phase management unit 306 of the receiving terminal 308 stores, inassociation with the phase number, the pairing value included in thereceived pairing finalization start message 5301. The phase managementunit 306 stores, for the phase number, “1” indicating the pairingpreparation phase. Afterward, the communication unit 309 transmits apairing finalization request message to the pairing server 314.

Specific processing of transmitting the pairing finalization requestmessage is the same as the processing in Step S4305 described inEmbodiment 4.

(Step S5206)

Processing the same as in Step S4306 in Embodiment 4 (Step S1505 inEmbodiment 1) is performed.

(Steps S5207 and S5208)

Processing the same as in Steps S4307 and S4308 in Embodiment 4 isperformed.

(Steps S5209 and S5210)

Processing the same as in Steps S4309 and S4310 in Embodiment 4 (StepsS1508 and S1509 in Embodiment 1) is performed.

The description on processing in the pairing finalization phase endshere.

Through the above processing, the transmitting terminal 301 and thereceiving terminal 308 are paired. In this embodiment, the receivingterminal 308 is capable of obtaining the terminal ID of the transmittingterminal 301 (the transmitting terminal ID). Thus, afterward, using thetransmitting terminal ID, the receiving terminal 308 is allowed toshare, with the transmitting terminal 301, content such as photos andvideo held by the transmitting terminal 301.

It is to be noted that the transmitting terminal 301 and the receivingterminal 308 may share content in any way as long as they use the resultof pairing. For example, the pairing server 314 may control thecommunication between the transmitting terminal 301 and the receivingterminal 308 by referring to the pairing management table 315 a so as totransfer, to the receiving terminal 308, content such as photos receivedfrom the transmitting terminal 301. Furthermore, the pairing server 314may control the communication between the transmitting terminal 301 andthe receiving terminal 308 by referring to the pairing management table315 a so that content such as photos uploaded by the transmittingterminal 301 is downloadable by the receiving terminal 308.

As above, in the communication control system 4700 according to thisembodiment, the transmitting terminal 301 and the receiving terminal 308are paired when the pairing value transmitted from the transmittingterminal 301 to the pairing server 314 matches, in the pairing server314, the pairing value transmitted from the receiving terminal 308 tothe pairing server 314. Since a sufficiently large random number is usedas the pairing value, it will not happen that the transmitting terminalis paired with another receiving terminal which performs differentpairing processing. In other words, the data transmitted from thetransmitting terminal will not be received by a receiving terminal whichis not supposed to receive the data.

Furthermore, in the communication control system 4700 according to thisembodiment, the receiving mobile phone 323 determines whether or not theconverted address values match, and therefore, it will not happen thatwhen a malicious recipient who receives the shared ID from the sendertransfers the shared ID to another person, and the other person inputsthe transferred shared ID into the receiving terminal, the photoassociated with the shared ID can be received.

Furthermore, in the communication control system 4700 according to thisembodiment, since the pairing server 314 uses the communication devicemanagement table to manage the sets of the terminal and the mobilephone, it will not happen that when a malicious recipient inputs sharedID into a receiving terminal of another person, the photo associatedwith that shared ID can be received.

Although the communication control system according to an implementationof the present invention has been described above based on theembodiments, the present invention is not limited to these embodiments.Without departing from the scope of the present invention, the presentinvention includes an embodiment with some modifications on Embodimentsthat are conceived by a person skilled in the art, or an embodimentobtained through combinations of the constituents of differentEmbodiments.

For example, in each of the above embodiments described above, thecommunication between the transmitting terminal 301 and the pairingserver 313 and the communication between the receiving terminal 308 andthe pairing server 314 may each use a secure authenticated channel suchas secure sockets layer (SSL). This leads to security improvement in thecommunication between the transmitting terminal 301 or the receivingterminal 308 and the pairing server 314 so that an identity theft of aterminal and a leakage of a pairing value in the communication path canbe reduced.

Furthermore, it may be possible to apply digital signatures such as RSAto the pairing value and the converted address value in each of theabove embodiments. By doing so, the occurrence of tampering with thepairing value and the converted address value can be reduced.

Furthermore, in each of the above embodiments, the pairing server 314may return an error message when receiving no pairing finalizationrequest messages within a predetermined period of time aftertransmitting a pairing request message. By doing so, the occurrence ofmistaken pairing of the terminals due to, for example, an attack by amalicious user terminal can be reduced.

Furthermore, in each of the above embodiments, each of the pairing valueand the converted address value may be assigned with its creation dateand time. By doing so, when performing the determination on the pairingvalue and the converted address value, it is possible to compare thecreation date and time with the current date and time to delete olddata.

Furthermore, in each of the above embodiments, the pairing server 314may restrict receiving of a message from a terminal when error messageshave been transmitted to the terminal a predetermined number of times ormore in response to the pairing request message or the pairingfinalization request message. Specifically, the pairing server 314 maybe set not to receive messages from that terminal at all or within apredetermined period of time. By doing so, an increase in the load ofcommunication processing on the pairing server 314 due to, for example,a breakdown or a malfunction of the terminal and an attack by amalicious user terminal can be reduced.

Furthermore, the transmitting terminal 301 and the receiving terminal308 transmit the converted communication device values to the pairingserver 314 in each of the above embodiments, but, instead of theconverted communication device values, terminal ID and mobile phone IDbefore converted may be transmitted to the pairing server 314. By sodoing, in return for the transmission of a unique identifier of themobile phone to the pairing server, it becomes possible to reduce theconversion-related burden on the terminal.

Furthermore, although the pairing server manages the set of thetransmitting mobile phone and the transmitting terminal and the set ofthe receiving mobile phone and the receiving terminal in the process ofthe communication device registration phase in each of the aboveembodiments, it may be that the pairing server does not perform themanagement and instead, the transmitting terminal manages a set of thetransmitting mobile phone and the transmitting terminal while thereceiving terminal manages a set of the receiving mobile phone and thereceiving terminal. In this case, the determination on a combination ofthe mobile phone and the terminal is performed by the terminal. By doingso, it is possible to reduce the processing load on the pairing server.

Furthermore, although the communication address is converted by the dataconversion unit into the converted data in each of the above embodiment,the communication address does not always need to be converted intoconverted data. In this case, each device does not need to include thedata conversion unit.

Furthermore, although there is the communication device registrationphase in each of the above embodiments, it is not always necessary toprovide the communication device registration phase. In this case, it isnot necessary to determine whether or not the set of the mobile phoneand the terminal to be used for pairing has been stored in thecommunication device management table.

Furthermore, part or all of the constituents of the pairing server 314,the transmitting terminal 301, or the receiving terminal 308 in each ofthe above embodiments may be provided in one system large scaleintegration (LSI). For example, the phase management unit 316 of thepairing server 314 may be provided in the system LSI.

The system LSI is a super multifunctional LSI manufactured byintegrating plural components into one chip and is specifically acomputer system which includes a microprocessor, a read only memory(ROM), a random access memory (RAM) and so on. On the RAM, a computerprogram has been stored. When the microprocessor operates according tothe computer program, the system LSI implements its functions.

The name used here is system LSI, but it may also be called IC, LSI,super LSI, or ultra LSI depending on the degree of integration.Moreover, ways to achieve integration are not limited to the LSI, and adedicated circuit or a general purpose processor can also achieve theintegration. A field programmable gate array (FPGA) that can beprogrammed after manufacturing LSIs or a reconfigurable processor thatallows re-configuration of the connection or setting of a circuit cellwithin an LSI can be used.

In the future, with advancement in semiconductor technology, a brand-newor derivative technology may replace LSI and using such technology, thefunctional blocks can be integrated. This includes, as a possibility, anapplication of biotechnology.

Furthermore, the present invention may be implemented in one or moreembodiments as the pairing server 314, the transmitting terminal 301, orthe receiving terminal 308 which includes such a characteristicprocessing unit. Furthermore, the present invention may be implementedin one or more embodiments as a communication control method whichincludes, as a step, a characteristic processing unit included in thepairing server 314, the transmitting terminal 301, or the receivingterminal 308. Furthermore, the present invention may be implemented inone or more embodiments as a computer program which causes a computer toexecute each characteristic step included in the communication controlmethod. In addition, the present invention may be implemented in one ormore embodiments as a computer-readable non-transitory recording mediumsuch as compact disc read only memory (CD-ROM) on which such a computerprogram has been recorded.

It is to be noted that, in each of the above embodiments, eachconstituent may be composed of dedicated hardware or implemented byexecuting a software program suited to the constituent. Each constituentmay be implemented by reading and executing, by means of a programexecution unit such as a CPU or a processor, a software program recordedon a recording medium such as hard disk or semiconductor memory. Here,the software which implements the server device or the like in each ofthe above embodiments is a program as follows.

Specifically, this program causes a computer to: determine, when a firstrequest which requests pairing is received from the first communicationdevice and a second request which requests pairing is received from thesecond communication device, whether or not a pairing identifierincluded in the first request and a pairing identifier included in thesecond request match and whether or not communication device informationincluded in the first request and communication device informationincluded in the second request match, the communication deviceinformation being information on a device capable of communicating withthe second communication device; and pair the first communication deviceand the second communication device using the first device identifierincluded in the first request and the second device identifier includedin the second request when it is determined that the pairing identifierincluded in the first request and the pairing identifier included in thesecond request match and that the communication device informationincluded in the first request and the communication device informationincluded in the second request match.

INDUSTRIAL APPLICABILITY

The communication control system according to an implementation of thepresent invention is useful as a content sharing system in which contentsuch as photos and video can be shared by acquaintances.

REFERENCE SIGNS LIST

-   100 Photo sharing system-   101 Transmitting terminal-   102 Receiving terminal-   103 Photo sharing server-   300, 2700, 3300, 3700, 4700 Communication control system-   301 Transmitting terminal-   302, 311, 4701, 4702 Data conversion unit-   303, 2701, 3301 Pairing value generation unit-   304, 312, 320, 326 Device connection unit-   305, 309, 317, 321, 325 Communication unit-   306, 310, 316 Phase management unit-   307, 313 Terminal ID holding unit-   308 Receiving terminal-   314 Pairing server-   315 Pairing management unit-   315 a Pairing management table-   316 a First storing unit-   316 a Second storing unit-   316 c First determination unit-   316 d Second determination unit-   316 e Pairing unit-   318 Communication device management unit-   318 a Communication device management table-   319 Transmitting mobile phone-   322, 324 Address management unit-   323 Receiving mobile phone-   3701, 4703 Determination unit

1-13. (canceled)
 14. A communication control system comprising: a firstcommunication device; a second communication device; a thirdcommunication device capable of communicating with the firstcommunication device; a fourth communication device capable ofcommunicating with the second communication device and the thirdcommunication device; and a server device connected to each of the firstcommunication device and the second communication device via a network,wherein the communication control system pairs the first communicationdevice and the second communication device to control communicationbetween the first communication device and the second communicationdevice, the third communication device includes: a management unitconfigured to hold communication device information that is informationon the fourth communication device; and a first transmitting unitconfigured to transmit the held communication device information to thefirst communication device, the first communication device includes: apairing identifier generation unit configured to generate a pairingidentifier when the communication device information is received fromthe third communication device; a second transmitting unit configured totransmit, to the server device, a first request including a first deviceidentifier of the first communication device, the communication deviceinformation, and the generated pairing identifier; and a thirdtransmitting unit configured to transmit the generated pairingidentifier to the third communication device, the third communicationdevice further includes a fourth transmitting unit configured to, whenthe pairing identifier is received from the first communication device,transmit the received pairing identifier to the fourth communicationdevice, the fourth communication device includes a fifth transmittingunit configured to, when the pairing identifier is received from thethird communication device, transmit communication device informationand the received pairing identifier to the second communication device,the communication device information being information on the fourthcommunication device which is previously held in the fourthcommunication device, the second communication device includes a sixthtransmitting unit configured to transmit a second request to the serverdevice when the communication device information and the pairingidentifier are received from the fourth communication device, the secondrequest including a second device identifier of the second communicationdevice, the received communication device information, and the receivedpairing identifier, and the server device includes: a determination unitconfigured to, when the first request is received from the firstcommunication device and the second request is received from the secondcommunication device, determine whether or not the pairing identifierincluded in the first request and the pairing identifier included in thesecond request match and whether or not the communication deviceinformation included in the first request and the communication deviceinformation included in the second request match; and a pairing unitconfigured to pair the first communication device and the secondcommunication device using the first device identifier included in thefirst request and the second device identifier included in the secondrequest when it is determined that the pairing identifier included inthe first request and the pairing identifier included in the secondrequest match and that the communication device information included inthe first request and the communication device information included inthe second request match.
 15. The communication control system accordingto claim 14, wherein the communication device information indicates acommunication address of the fourth communication device, and the fourthtransmitting unit is configured to transmit the pairing identifier tothe fourth communication device using the communication addressindicated in the communication device information.
 16. The communicationcontrol system according to claim 14, wherein the first communicationdevice further includes a first data conversion unit configured toconvert the communication device information using a one-way function,the first request includes the communication device informationresulting from the conversion, the second communication device furtherincludes a second data conversion unit configured to convert thecommunication device information using the one-way function, and thesecond request includes the communication device information resultingfrom the conversion.
 17. The communication control system according toclaim 14, wherein the first transmitting unit is configured to transmitthe communication device information to the first communication deviceusing near field communication, and the third transmitting unit isconfigured to transmit the pairing identifier to the third communicationdevice using the near field communication.
 18. A communication controlsystem comprising: a first communication device; a second communicationdevice; a third communication device capable of communicating with thefirst communication device; a fourth communication device capable ofcommunicating with the second communication device and the thirdcommunication device; and a server device connected to each of the firstcommunication device and the second communication device via a network,wherein the communication control system pairs the first communicationdevice and the second communication device to control communicationbetween the first communication device and the second communicationdevice, the third communication device includes: a management unitconfigured to hold communication device information that is informationon the fourth communication device; and a first transmitting unitconfigured to transmit the held communication device information to thefirst communication device, the first communication device includes asecond transmitting unit configured to transmit, to the server device, afirst request including a first device identifier of the firstcommunication device, and the communication device information receivedfrom the third communication device, the server device includes: apairing identifier generation unit configured to generate a pairingidentifier; and a third transmitting unit configured to transmit thegenerated pairing identifier to the first communication device, thefirst communication device further includes a fourth transmitting unitconfigured to transmit, to the third communication device, the pairingidentifier received from the server device, the third communicationdevice further includes a fifth transmitting unit configured to, whenthe pairing identifier is received from the first communication device,transmit the received pairing identifier to the fourth communicationdevice, the fourth communication device includes a sixth transmittingunit configured to, when the pairing identifier is received from thethird communication device, transmit communication device informationand the received pairing identifier to the second communication device,the communication device information being information on the fourthcommunication device which is previously held in the fourthcommunication device, the second communication device includes a seventhtransmitting unit configured to transmit a second request to the serverdevice when the communication device information and the pairingidentifier are received from the fourth communication device, the secondrequest including a second device identifier of the second communicationdevice, the received communication device information, and the receivedpairing identifier, the server device further includes: a determinationunit configured to, when the first request is received from the firstcommunication device and the second request is received from the secondcommunication device, determine whether or not the pairing identifiergenerated by the pairing identifier generation unit and the pairingidentifier included in the second request match and whether or not thecommunication device information included in the first request and thecommunication device information included in the second request match;and a pairing unit configured to pair the first communication device andthe second communication device using the first device identifierincluded in the first request and the second device identifier includedin the second request when it is determined that the pairing identifiergenerated by the pairing identifier generation unit and the pairingidentifier included in the second request match and that thecommunication device information included in the first request and thecommunication device information included in the second request match.19. A communication control system comprising: a first communicationdevice; a second communication device; a third communication devicecapable of communicating with the first communication device; a fourthcommunication device capable of communicating with the secondcommunication device and the third communication device; and a serverdevice connected to each of the first communication device and thesecond communication device via a network, wherein the communicationcontrol system pairs the first communication device and the secondcommunication device to control communication between the firstcommunication device and the second communication device, the thirdcommunication device includes: a pairing identifier generation unitconfigured to generate a pairing identifier; a management unitconfigured to hold communication device information that is informationon the fourth communication device; and a first transmitting unitconfigured to transmit, to the first communication device, the pairingidentifier generated by the pairing identifier generation unit and theheld communication device information, the first communication deviceincludes: a second transmitting unit configured to transmit, to theserver device, a first request including a first device identifier ofthe first communication device, and the communication device informationand the pairing identifier received from the third communication device;and a third transmitting unit configured to transmit the pairingidentifier to the third communication device, the third communicationdevice further includes a fourth transmitting unit configured totransmit, to the fourth communication device, the pairing identifiergenerated by the pairing identifier generation unit, the fourthcommunication device includes a fifth transmitting unit configured to,when the pairing identifier is received from the third communicationdevice, transmit communication device information and the receivedpairing identifier to the second communication device, the communicationdevice information being information on the fourth communication devicewhich is previously held in the fourth communication device, the secondcommunication device includes a sixth transmitting unit configured totransmit a second request to the server device when the communicationdevice information and the pairing identifier are received from thefourth communication device, the second request including a seconddevice identifier of the second communication device, the receivedcommunication device information, and the received pairing identifier,the server device includes: a determination unit configured to, when thefirst request is received from the first communication device and thesecond request is received from the second communication device,determine whether or not the pairing identifier included in the firstrequest and the pairing identifier included in the second request matchand whether or not the communication device information included in thefirst request and the communication device information included in thesecond request match; and a pairing unit configured to pair the firstcommunication device and the second communication device using the firstdevice identifier included in the first request and the second deviceidentifier included in the second request when it is determined that thepairing identifier included in the first request and the pairingidentifier included in the second request match and that thecommunication device information included in the first request and thecommunication device information included in the second request match.20. A communication control system comprising: a first communicationdevice; a second communication device; a third communication devicecapable of communicating with the first communication device; a fourthcommunication device capable of communicating with the secondcommunication device and the third communication device; and a serverdevice connected to each of the first communication device and thesecond communication device via a network, wherein the communicationcontrol system pairs the first communication device and the secondcommunication device to control communication between the firstcommunication device and the second communication device, the thirdcommunication device includes: a management unit configured to holdcommunication device information that is information on the fourthcommunication device; and a first transmitting unit configured totransmit the held communication device information to the firstcommunication device, the first communication device includes: a pairingidentifier generation unit configured to generate a pairing identifierwhen the communication device information is received from the thirdcommunication device; a first conversion unit configured to convert,using a predetermined conversion method, the communication deviceinformation received from the third communication device, to generatefirst converted data; a second transmitting unit configured to transmit,to the server device, a first request including a first deviceidentifier of the first communication device and the generated pairingidentifier; and a third transmitting unit configured to transmit thepairing identifier and the first converted data to the thirdcommunication device, the third communication device further includes afourth transmitting unit configured to, when the pairing identifier andthe first converted data are received from the first communicationdevice, transmit the received pairing identifier and the received firstconverted data to the fourth communication device, the fourthcommunication device includes a fifth transmitting unit configured to,when the pairing identifier and the first converted data are receivedfrom the third communication device, transmit communication deviceinformation, the received pairing identifier, and the received firstconverted data to the second communication device, the communicationdevice information being information on the fourth communication devicewhich is previously held in the fourth communication device, the secondcommunication device includes: a second conversion unit configured to,when the communication device information, the pairing identifier, andthe first converted data are received from the fourth communicationdevice, convert the communication device information using thepredetermined conversion method, to generate second converted data; afirst determination unit configured to determine whether or not thefirst converted data and the second converted data match; and a sixthtransmitting unit configured to transmit a second request to the serverdevice when it is determined that the first converted data and thesecond converted data match, the second request including a seconddevice identifier of the second communication device and the pairingidentifier, and the server device includes: a second determination unitconfigured to, when the first request is received from the firstcommunication device and the second request is received from the secondcommunication device, determine whether or not the pairing identifierincluded in the first request and the pairing identifier included in thesecond request match; and a pairing unit configured to pair the firstcommunication device and the second communication device using the firstdevice identifier included in the first request and the second deviceidentifier included in the second request when it is determined that thepairing identifier included in the first request and the pairingidentifier included in the second request match.
 21. A communicationcontrol system comprising: a first communication device; a secondcommunication device; a third communication device capable ofcommunicating with the first communication device; a fourthcommunication device capable of communicating with the secondcommunication device and the third communication device; and a serverdevice connected to each of the first communication device and thesecond communication device via a network, wherein the communicationcontrol system pairs the first communication device and the secondcommunication device to control communication between the firstcommunication device and the second communication device, the firstcommunication device includes: a pairing identifier generation unitconfigured to generate a pairing identifier; a first transmitting unitconfigured to transmit, to the server device, a first request includinga first device identifier of the first communication device and thegenerated pairing identifier; and a second transmitting unit configuredto transmit the pairing identifier to the third communication device,the third communication device includes: a management unit configured tohold communication device information that is information on the fourthcommunication device; a first conversion unit configured to convert theheld communication device information using a predetermined conversionmethod, to generate first converted data; and a third transmitting unitconfigured to, when the pairing identifier is received from the firstcommunication device, transmit the received pairing identifier and thefirst converted data to the fourth communication device, the fourthcommunication device includes: a second conversion unit configured toconvert communication device information using the predeterminedconversion method, to generate second converted data, when the pairingidentifier and the first converted data are received from the thirdcommunication device, the communication device information beinginformation on the fourth communication device which is previously heldin the fourth communication device; a first determination unitconfigured to determine whether or not the first converted data and thesecond converted data match; and a fourth transmitting unit configuredto transmit the received pairing identifier to the second communicationdevice when it is determined that the first converted data and thesecond converted data match, the second communication device includes afifth transmitting unit configured to transmit a second request to theserver device when the pairing identifier is received from the fourthcommunication device, the second request including a second deviceidentifier of the second communication device and the received pairingidentifier, and the server device includes: a second determination unitconfigured to, when the first request is received from the firstcommunication device and the second request is received from the secondcommunication device, determine whether or not the pairing identifierincluded in the first request and the pairing identifier included in thesecond request match; and a pairing unit configured to pair the firstcommunication device and the second communication device using the firstdevice identifier included in the first request and the second deviceidentifier included in the second request when it is determined that thepairing identifier included in the first request and the pairingidentifier included in the second request match.
 22. A communicationcontrol method which is performed in communication control systemincluding: a first communication device; a second communication device;a third communication device capable of communicating with the firstcommunication device; a fourth communication device capable ofcommunicating with the second communication device and the thirdcommunication device; and a server device connected to each of the firstcommunication device and the second communication device via a network,the communication control system pairing the first communication deviceand the second communication device to control communication between thefirst communication device and the second communication device, and thecommunication control method comprising: transmitting communicationdevice information from the third communication device to the firstcommunication device, the communication device information beinginformation on the fourth communication device; generating a pairingidentifier in the first communication device when the communicationdevice information is received from the third communication device;transmitting a first request from the first communication device to theserver device, the first request including a first device identifier ofthe first communication device, the received communication deviceinformation, and the generated pairing identifier; transmitting thegenerated pairing identifier from the first communication device to thethird communication device; transmitting, when the pairing identifier isreceived from the first communication device, the received pairingidentifier from the third communication device to the fourthcommunication device; transmitting, when the pairing identifier isreceived from the third communication device, communication deviceinformation and the received pairing identifier from the fourthcommunication device to the second communication device, thecommunication device information being information on the fourthcommunication device which is previously held in the fourthcommunication device; transmitting a second request from the secondcommunication device to the server device when the communication deviceinformation and the pairing identifier are received from the fourthcommunication device, the second request including a second deviceidentifier of the second communication device, the receivedcommunication device information, and the received pairing identifier;determining, in the server device when the first request is receivedfrom the first communication device and the second request is receivedfrom the second communication device, whether or not the pairingidentifier included in the first request and the pairing identifierincluded in the second request match and whether or not thecommunication device information included in the first request and thecommunication device information included in the second request match;and pairing, in the server device, the first communication device andthe second communication device using the first device identifierincluded in the first request and the second device identifier includedin the second request when it is determined that the pairing identifierincluded in the first request and the pairing identifier included in thesecond request match and that the communication device informationincluded in the first request and the communication device informationincluded in the second request match.
 23. A server device connected toeach of a first communication device and a second communication devicevia a network, for pairing the first communication device and the secondcommunication device to control communication between the firstcommunication device and the second communication device, the serverdevice comprising: a determination unit configured to, when a firstrequest which requests pairing is received from the first communicationdevice and a second request which requests pairing is received from thesecond communication device, determine whether or not a pairingidentifier included in the first request and a pairing identifierincluded in the second request match and whether or not communicationdevice information included in the first request and communicationdevice information included in the second request match, thecommunication device information being information on a device capableof communicating with the second communication device; and a pairingunit configured to pair the first communication device and the secondcommunication device using the first device identifier included in thefirst request and the second device identifier included in the secondrequest when it is determined that the pairing identifier included inthe first request and the pairing identifier included in the secondrequest match and that the communication device information included inthe first request and the communication device information included inthe second request match.
 24. The server device according to claim 23,wherein the server device is provided as an integrated circuit.
 25. Acommunication control method for pairing a first communication deviceand a second communication device which are connected via a network, tocontrol communication between the first communication device and thesecond communication device, the communication control methodcomprising: determining, when a first request which requests pairing isreceived from the first communication device and a second request whichrequests pairing is received from the second communication device,whether or not a pairing identifier included in the first request and apairing identifier included in the second request match and whether ornot communication device information included in the first request andcommunication device information included in the second request match,the communication device information being information on a devicecapable of communicating with the second communication device; andpairing the first communication device and the second communicationdevice using the first device identifier included in the first requestand the second device identifier included in the second request when itis determined that the pairing identifier included in the first requestand the pairing identifier included in the second request match and thatthe communication device information included in the first request andthe communication device information included in the second requestmatch.
 26. A computer-readably non-transitory recording medium havingrecorded thereon a program for causing a computer to execute thecommunication control method according to claim 25.